On Tue, Jun 30, 2009 at 03:33, Theodore Ts'o<tytso@xxxxxxx> wrote: > > There was a very good reason why uuid state files were in > /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. Fedora and SUSE at least have this initscript. > By placing those files in /var/lib/libuuid, it avoided this problem. > > A similar issue is why the clock state file is in /var/lib instead of > /var/run. That becomes only an issue, if systems are set up to let the lib magically start the daemon, which needs to be setuid then, right? Kay -- 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
