'Twas brillig, and Pascal Terjan at 24/01/13 00:24 did gyre and gimble: > I was looking at perl-Apache2-DebugFilter build failure > > In the test it starts an apache which fails as it uses > http://httpd.apache.org/docs/trunk/rewrite/rewritemap.html#prg which > uses a mutex stored in /run/httpd/ > > [Wed Jan 23 23:49:55.962405 2013] [core:emerg] [pid 55277] > (13)Permission denied: AH00023: Couldn't create the rewrite-map mutex > (file /run/httpd/rewrite-map.55277) > > That directory is now owned by root so it can't be used for anything > except creating the httpd.pid > > $ cat /usr/lib/tmpfiles.d/httpd.conf > d /run/httpd 755 root root > > Fedora uses "d /run/httpd 710 root apache" which doesn't help in > this case but fixes other problems > > In the past (Mageia 1) runtimedir was /var/run directly so it was > possible to create mutex files there for any user
Hmm, not sure what you mean here. [colin@mga2 ~]$ ls -ld /var/run drwxr-xr-x 38 root root 4096 Jan 23 04:04 /var/run/ That dir is also owned by root with 755 perm. It shouldn't make any odds to permissions. > Is there a list of packages which have moved to subdirectories of /run > and may now be broken too? Again I don't think so. The fact that /var/run is just a symlink now should be irrelevant. Also the fact that /run is mounted on tmpfs vs real fs again should not alter permissions in any way - all it really means is that a) it'll be cleared at boot b) we have to create files/folders with appropriate ownership/perms during early boot via tmpfiles. So I'm not really sure what you're saying here, but I don't think it is any more broken now than it would have been before using /var/run directly. Col -- Colin Guthrie colin(at)mageia.org http://colin.guthr.ie/ Day Job: Tribalogic Limited http://www.tribalogic.net/ Open Source: Mageia Contributor http://www.mageia.org/ PulseAudio Hacker http://www.pulseaudio.org/ Trac Hacker http://trac.edgewall.org/
