In our environment, our ArcGIS Server user has a umask command in its profile that sets its create permissions to 640 (the '4' indicates members of the same group should get read and execute permissions - the execute permissions are necessary in case it's a directory so the group member can "cd" into it). Since the ArcGIS Server is started with the ArcGIS Server user's account, we expected it to use those settings. Instead, new log files continue to be created with 600 permissions. So, is ArcGIS Server code overriding the umask settings somehow?
Yes, ArcGIS Server will create a file with access for ArcGIS Server account only. It is recommended not to access the log files from outside of ArcGIS Server Manager.
Sorry cut off - drwxr-xr-x
I'm responding to a very old post here; hopefully someone will see this.
We need to be able to track these logs using a log-aggregator, in our case 'splunk'. It will be simple enough to add the 'splunk' user to the arcgis group. But the arcgis directories are stored with 700 permissions, and the log files with 600 permissions.
We want to use 750 and 640 permissions, so that a member of the same GROUP can read the files.
How can we override the umask associated with the creation of these log files and their parent directories?
Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.