Skip to end of metadata
Go to start of metadata

NMIS8 Unix File Permissions

NMIS normally runs under it's own user, all files under the nmis directory should be owned by nmis and in the group nmis.  In order to allow apache to serve the CGI scripts, the nmis group is added to the apache user.

NMIS supplies several tools/scripts to help you get the permissions set correctly and to check that nothing is out of place.

Basic File Permissions

Make nmis user and group own all the files. 

If you decide on a different user and group name, update the NMIS Configuration Config.nmis accordingly.

One of the joys of Unix is granular file permissions, one of the frustrations of Unix is granular file permissions.  To assist we have added a handy script in the admin directory <nmisdir>/admin/ which will read the NMIS Configuration and fix the permissions accordingly. 

Sample output from command 

Apache User File Permissions

As described in the installation guide, the HTTP Daemon user needs to be able to read and write the NMIS files, so you need to put the owner of the HTTP Daemon, this is usually the user apache or www-data.  You can determine by running: 

So the HTTP Daemon user is apache in this example.

Modify the Apache user groups 

Then restart the HTTP Daemon 

SELinux Troubleshooting Tip

Sometimes there are things happening on Linux systems which don't make sense, many times it is because SELinux is preventing things.  You can spend alot of time getting SELinux to behave, or you can put it in permissive mode, or disable it, in the NMIS VM it has been disabled.

Much information to be found with Google, the following describes either option.

NMIS Tools and scripts provides 2 methods for checking the directory structure of nmis and ensuring that the structure is complete and has the correct permissions (based on your Config.nmis).  Running type=audit will report discrepancies between your structure and what is required, type=config will fix those errors 

Additonally, the script will go through and set the permissions on each file to ensure that NMIS can access the files it requires to operate normally 

  • No labels