Re: uuidd: move uuidd files from /var/lib/libuuid to /var/run/uuidd

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tuesday 30 June 2009 14:29:05 Karel Zak wrote:
> On Tue, Jun 30, 2009 at 01:37:23PM -0400, Mike Frysinger wrote:
> > On Tuesday 30 June 2009 04:37:08 Karel Zak wrote:
> > > On Tue, Jun 30, 2009 at 09:51:15AM +0200, Matthias König wrote:
> > > > 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"
> >
> > well if it's only one file, i think it'd be better to use the misc dir
> > rather than creating a dedicated dir for one file
> > /var/lib/misc/libuuid-clock.txt
>
>  The daemon is not (usually) running with root permissions.
>
> > makes things easier on distros as they only have to make sure
> > /var/lib/misc exists in common init scripts ... they dont have to create
> > a dedicated init script to just make sure /var/lib/libuuid exists.
>
>  The /var/lib/uuidd directory is usually created during package
>  installation. We need the init script for /var/run/uuidd (where we
>  store pidfile and socket).

and the package install can just as easily do:
install -m 644 -g uuid -u uuid /var/lib/misc/libuuid-clock.txt
(command may be wrong, i just typed it w/out checking)

>  Ted's suggestion is to use /var/lib/libuuid for all files, so you
>  needn't init scripts at all and you can directly execute the daemon
>  (setuid) from the library.
>
>  I (and Kay) believe that the daemon should be explicitly enabled (by
>  chkconfig or so) and /var/run/uuidd initialized by init scripts. The
>  daemon could be executed from the init script or on-demand from the
>  library (you need setuid version of course).

i guess if it's a configure flag like someone suggested, we can let distros do 
whatever crazy stuff they feel is best.  in an embedded setup, the on-demand 
execution would make more sense ...
-mike

Attachment: signature.asc
Description: This is a digitally signed message part.


[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux