BobDid you try "umask 022" in the init.d script as well?What is the umask for the user that is running Tomcat?I am assuming you restarted Tomcat after updating the startup.sh.On Thu, Apr 28, 2016 at 4:07 PM, Frank <firstname.lastname@example.org> wrote:-FrankKind regards,Any other ideas?Hi Bob,Thanks for the suggestion. I added 'umask 002' to the tomcat7/bin/startup.sh script. Sadly it did nothing. Here are some files from my testing. These are logo files the application receives and stores on disk
-rw-r--r-- 1 tomcat7 tomcat7 17771 Apr 28 14:48 69ff2f84bf5ffa08
-rw-r--r-- 1 tomcat7 tomcat7 6247 Apr 28 14:49 7eeb290334835693
-rw-r--r-- 1 tomcat7 tomcat7 18683 Apr 28 15:02 4c0df621ab060c47On Thu, Apr 28, 2016 at 3:08 PM, sigzero <email@example.com> wrote:Try setting it in: tomcat/bin/startup.shI think it is just "umask 002" not "umask=002" as well from everything I have seen and read.
BobOn Thu, Apr 28, 2016 at 2:27 PM, Frank <firstname.lastname@example.org> wrote:-FrankKind regards,Thanks in advance.Is there a place where I can configure the application itself to create files with these looser default permissions?it doesn't affect the permissions on files created by the application.umask=022 -to- umask=002We have a packaged installation of Tomcat7 and we drop our .WAR file in /var/lib/tomcat7/webapps/. We start the application using the /etc/init.d/tomcat7 script (or `sudo service tomcat7 start`). We have some other things (like newrelic) which we set to run in a /usr/share/tomcat7/bin/setenv.sh scriptHi,Ubuntu Server 14.04LTSTomcat 7.0.52Groovy 2.0.8I have a Groovy application which I run within Tomcat7. It creates files with permissions of 644 and I would like it to create them with permissions of 664 instead (group read/writable).
I've tried changing the umask setting in the /etc/init.d/tomcat7 script from