Bug#746279: systemd: wrong permissions on non-persistent /run/log/journal

Alessandro Ghedini ghedo at debian.org
Mon Apr 28 19:01:55 BST 2014


On Mon, Apr 28, 2014 at 07:39:10PM +0200, Michael Biebl wrote:
> Am 28.04.2014 19:19, schrieb Alessandro Ghedini:
> > I also had to add the line:
> > 
> >     m /run/log/journal/%m/system.journal 2755 root systemd-journal - -
> > 
> > to /usr/lib/tmpfiles.d/systemd.conf, because, while the directory got the right
> > owner, the journal file did not (it was still root:root).
> > 
> 
> Shouldn't the sticky bit ensure that subdirectories get the correct
> permissions once they are created?

If I understand things correctly "m" only works on already existing directories
and files, which means system.journal is already there with the wrong usr:grp,
and changing the owner of a sticky directory won't change the owner of the files
it contains... unless you do a recursive chown/chmod, which, I just noticed,
is what systemd does since commit a606871da50 (it uses "Z" instead of "m").

I'm gonna try that and report back.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20140428/8c51d63c/attachment-0002.sig>


More information about the Pkg-systemd-maintainers mailing list