|
From: Leif M. <le...@ta...> - 2005-11-07 07:30:47
|
Juergen
Thanks for suggesting this. It has been implemented for the 3.2.0
release and is
in CVS.
From the release notes:
* Add the ability to specify integer property values in base 8 or 16 in
addition to base 10. Base 8 values start with a '0' and base 16 values
start with a '0x'.
* Make it possible to set the umask on all files created by the Wrapper
as well as the default umask of files created by the JVM. Added new
wrapper.umask, wrapper.java.umask, wrapper.pidfile.umask,
wrapper.java.pidfile.umask, wrapper.java.idfile.umask,
wrapper.statusfile.umask, wrapper.java.statusfile.umask,
wrapper.anchorfile.umask, and wrapper.logfile.umask properties.
All of the detailed umask properties default to value of wrapper.umask.
Cheers,
Leif
Juergen Hermann wrote:
>Hi, we have set the umask to 027 before running
>the JSW in order to have the JVM generate no
>world readable files.
>
>The problem with this is that the files the JSW
>generates (log, pid-file, etc.) also use that
>umask, but we'd like to have the log-files
>world readable.
>
>So it would be nice if you were able to set the
>umask fpr the JVM process (and only for that)
>in wrapper.conf, and have the wrapper itself
>use the umask it is started with. Don't know if
>we'll write a patch for this, but I wanted to
>share the use-case anyway.
>
>
>
>Ciao, Jürgen
>
>
|