On Fri, Mar 06, 2009 at 03:48:55PM +0100, Josef Wolf wrote:
Hello,
With opensuse-11.1 and kde4, I have seen three times on two different boxes that the mode of /dev/null was changed to 600. This breaks lots of scripts, which assume /dev/null is writable by anybody.
The timestamp of /dev/null is also changed. Since chmod don't change the timestamp, this means the file is removed and recreated.
I think I found the guilty: it is the update of aaa_base. Check out the timestamp: raven:/var/log # ls -l --full-time /dev/null crw-rw-rw- 1 root root 1, 3 2009-03-06 15:03:22.680891742 +0100 /dev/null And then I found this in /var/log/pk_backend_zypp (I inserted whitespace to improve readability) 2009-03-06 15:03:19 <1> raven(13826) [zypp++] ExternalProgram.cc(start_program):210 Executing 'rpm' '--root' '/' '--dbpath' '/var/lib/rpm' '-U' '--percent' '--force' '--nodeps' '--' '/var/cache/zypp/packages/repo-update/rpm/x86_64/aaa_base-11.1-10007.14.1.x86_64.rpm' 2009-03-06 15:03:19 <1> raven(13826) [zypp++] ExternalProgram.cc(start_program):354 pid 13889 launched 2009-03-06 15:03:23 <1> raven(13826) [zypp++] ExternalProgram.cc(checkStatus):408 Pid 13889 successfully completed The question remains: why does this update remove and recreate /dev/null with wrong permissions? I have set umask to 0077 in /etc/bash.bashrc.local and used the updater applet in kde4. But IMHO the update should ignore this umask setting. Next question is: which files could be affected in addition? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org