Josh,
The wrapper.umask, wrapper.anchorfile.umask, wrapper.<etc>.umask
properties are all
designed to set the umask of the various files created by the wrapper itself.
You can specify the default umask for the Java process with wrapper.java.umask.
These properties are set within the Wrapper and must therefor be done before the
JVM is launched.
As I understand it, you are attempting to system properties within the JVM. The
Wrapper will not recognize any system properties set within the JVM.
Please add wrapper.java.umask to your wrapper.conf file.
http://wrapper.tanukisoftware.org/doc/english/prop-umask.html
You mentioned that you are writing a "pure java" implementation of the Wrapper?
You will always need the native binary and JNI library for the Wrapper
to function
correctly.
Cheers,
Leif
On Thu, Jun 26, 2008 at 11:39 PM, Joshua Sumali <js...@re...> wrote:
> Hi,
>
> I'm trying to use the pure java implementation of tanukiwrapper
> (Integration Method 3) and whenever I try to specify the umask to use,
> tanukiwrapper seems to ignore the setting. I've tried setting the umask
> with:
>
> -Dwrapper.umask=0077 on the command line, and
> System.setProperty("wrapper.umask","0077") in the actual code, but
> neither method seems to work, as any files created by the test
> application I'm working with still has 664 permissions instead of the
> expected 600. Am I doing something wrong, or is this perhaps a bug?
>
> Any help or comments appreciated.
>
> Thanks,
> Josh
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
|
