[
https://issues.apache.org/jira/browse/DAEMON-307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13799335#comment-13799335
]
Richard Thiemann commented on DAEMON-307:
-----------------------------------------
1.0.15 fixes DAEMON-280 correct?
./jsvc --help | grep ^jsvc
jsvc (Apache Commons Daemon) 1.0.15-dev
I'm still getting different results than you. And I can't determine why that
would be. I broke it down to the simplest of tests mimicking yours above.
./jsvc -debug -umask 0002 foobar
Switching umask back to 022 from 002
./jsvc -debug -umask 0022 foobar
Switching umask back to 022 from 022
This is running on CentOS 6.3 64-bit. Using the default system gcc compiler.
> -umask input values and correlating output pid file permissions
> ---------------------------------------------------------------
>
> Key: DAEMON-307
> URL: https://issues.apache.org/jira/browse/DAEMON-307
> Project: Commons Daemon
> Issue Type: Bug
> Components: Jsvc
> Affects Versions: 1.0.15
> Environment: CentOS 6.3 64-bit
> Reporter: Richard Thiemann
> Priority: Minor
>
> I'm passing the following input values to the -umask flag in a bourne shell
> script and get the following resulting file permissions on the pid file.
> umask | file permissions on PID file
> 0011 | 644
> 0002 | 644
> 0022 | 644
> 0003 | 644
> 0033 | 644
> 0004 | 640
> 0005 | 640
> 0055 | 600
> 0006 | 640
> 0072 | 604
> 0073 | 604
> Which I don't believe is the correct output.
> log messages from adding the -debug flag follow with the according -umask
> flag value
> -umask 0002 | Switching umask back to 022 from 002
> -umask 0022 | Switching umask back to 022 from 002
> -umask 0004 | Switching umask back to 022 from 002
> -umask 0072 | Switching umask back to 022 from 072
> -umask 0055 | Switching umask back to 022 from 055
> -umask 0066 | Switching umask back to 022 from 066
> -umask 0077 | Switching umask back to 022 from 077
--
This message was sent by Atlassian JIRA
(v6.1#6144)
