After uncommenting the following segment of "/etc/apache2/modules.d/47_mod_umask.conf" the behaviour was unexpected: # This is usefull for group-write-access, such as used in subversion # UMask 002 The proper UMask statement appears to be: UMask 0002 Reproducible: Always Steps to Reproduce: 1. 2. 3.
um... why *appears* to be? did you test it? didn't it work for "002" and did work for "0002"? I'd wonder when it wouldn't work with 002. hmm....
Yep, works with "0002" and doesn't work with "002". [I--] [ ] net-www/apache-2.0.54-r31 (2) is what I have installed. Could this have something to do with bug fizes/changes in later versions of Apache2? The umask command when executed as "umask 002" usually sets the umask to "0002" could this be the confusion? callan@wizard ~ $ umask 0022 callan@wizard ~ $ umask 002 callan@wizard ~ $ umask 0002
(In reply to comment #2) > Yep, works with "0002" and doesn't work with "002". > > [I--] [ ] net-www/apache-2.0.54-r31 (2) > > is what I have installed. Could this have something to do with bug fizes/changes > in later versions of Apache2? > > The umask command when executed as "umask 002" usually sets the umask to "0002" > could this be the confusion? > > callan@wizard ~ $ umask > 0022 > callan@wizard ~ $ umask 002 > callan@wizard ~ $ umask > 0002 AFAIK because the leading 0 in 0002 comes from programming language C/C++/... where this declares the number do have a base of 8, meaning this number is a octal number. While umasks are usually *always* specified octal it might be that the umask console tool will handle this. Looks like we've to look at mod_umask's sources, or just ask chipig on this issue ;)
Hi chipig, could you shed any light on this? Thanks! Best regards, CHTEKK.
mod_umask passes the configuration value straight to umask(2), so yes, this is interpreted as octal only with a 0 prefix. fixed in place (no revbump)
