-
Bug
-
Resolution: Fixed
-
Minor
-
None
-
RHEL 5.4
Hello,
When running hudson via winstone as below.
/usr/lib/jvm/java-1.6.0/bin/java -Dcom.sun.akuma.Daemon=daemonized -Djava.awt.headless=true -DHUDSON_HOME=/var/lib/hudson -jar /usr/lib/hudson/hudson.war --logfile=/var/log/hudson/hudson.log --daemon --httpPort=8080 --debug=9 --handlerCountMax=100 --handlerCountMaxIdle=20
The umask of all the files created are set as 027 rather than the user who invokes the processes umask.
For example a user with a umask of 022 runs hudson and a job and all the resulting files are set to 027.
This is because the Daemon.java file that is part of akuma has a call to
LIBC.umask(0027);
Please can this be made user configurable or use the inherent umask of the running user.
Thanks
Steve Goodliff
We are encountering this same issue with Hudson 1.353, and it is actually a big issue for us.
It would be great if this could be changed soon, or at least a workaround published.
We are looking at having to move our build process into shell scripts and then just have those shell scripts launched by the Hudson build process with the hope that it resolves this issue.