[systemd-devel] [HEADSUP] /var/lock and /var/lock/lockdev
Lennart Poettering
lennart at poettering.net
Fri Apr 1 06:18:56 PDT 2011
On Fri, 01.04.11 08:52, Zbigniew Jędrzejewski-Szmek (zbyszek at in.waw.pl) wrote:
>
> On 04/01/2011 12:33 AM, Lennart Poettering wrote:
> > Heya,
> >
> > A few minutes ago there was a discussion on #systemd involving lots of
> > folks (from various distros even), regarding the chaotic setup of
> > /var/lock on most distros. As it turns out every distro set this up
> > differently, and almost all of them insecurely in one way or another.
> >
> > I'd like to see this cleaned up and standardized in a secure way among
> > the distros, so here's what I propose for adoption:
> >
> > /var/lock should be root:root 0755 and the place for various system
> > service lock directories such as /var/lock/subsys or /var/lock/lvm.
> Hi,
> why not /run/lock ?
Well, both are equivalent. Since the FHS mentions /var/lock only so far
I referred to this directory via /var/lock.
Lennart
--
Lennart Poettering - Red Hat, Inc.
More information about the systemd-devel
mailing list