On Tue, Jun 30, 2009 at 09:51:15AM +0200, Matthias König wrote:
> Mike Frysinger <vapier@xxxxxxxxxx> wrote:
> > On Monday 29 June 2009 21:33:44 Theodore Ts'o wrote:
> > > There was a very good reason why uuid state files were in
Thanks for review.
> > > /var/lib/libuuid instead of /var/run/uuidd. Some distributions wipe all
> > > of /var/run on reboot. The problem is for security reasons uuidd has to
> > > run as the libuuid user --- and the problem is directory needs to be set
> > > up correctly with the right permissions so it can written by the setuid
> > > libuuid daemon. So if you are going to move files into /var/run/uuidd,
> > > on at least some distributions, util-linux-ng will also have to provide
> > > init scripts to set up the directory correctly each time at boot.
Yes, that's my plan.
> > >
> > > By placing those files in /var/lib/libuuid, it avoided this problem.
> >
> > what exactly is the purpose of these state files ? are they supposed to be
> > created fresh at every reboot, or are they expected to live across reboots ?
> > i think that is the question which should determine /var/run vs /var/lib, not
> > init.d issues.
>
> We are speaking of 3 different files here:
> 1. PID file for uuidd
> 2. request socket for uuidd
> 3. the clock.txt state file
>
> According to FHS PID files and sockets *must* be put in /var/run.
Definitely.
> The state file clock.txt should of course be kept in /var/lib, because
> it should remain valid after a reboot.
OK.
commit 6dc9c350bdaca48805fbd319867a0c62e79a4482
Author: Karel Zak <kzak@xxxxxxxxxx>
Date: Tue Jun 30 10:18:04 2009 +0200
Revert "libuuid: move clock state file from /var/lib to /var/run"
Karel
--
Karel Zak <kzak@xxxxxxxxxx>
--
To unsubscribe from this list: send the line "unsubscribe util-linux-ng" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
