3 Commits (8a2cbe2c6deb93ccfed58fd755c886fce16586a3)

Author	SHA1	Message	Date
Theodore Ts'o	3381a63c54	libuuid: Don't run uuidd if it would fail due to permission problems ... Some distributions don't like installing uuidd setuid or setgid. So if the setuid or setigid bit is not set with uuidd, and the current process does not have write access to the UUIDD work directory, don't try running uuidd, since it won't work properly. Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>	2009-06-30 22:36:28 -04:00
Theodore Ts'o	2165003bd5	uuidd: Use /var/lib/libuuid instead of /var/run/uuidd ... /var/run can get completely removed at reboot, and uuidd doesn't have permissions to recreate /var/run/uuidd. So instead use /var/lib/libuuidd for the unix domain socket and pid files. Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>	2007-12-17 15:12:04 -05:00
Theodore Ts'o	740837def7	Add uuidd daemon to prevent duplicate time-based UUID's ... Also store the clock sequence information in a state file in /var/lib/misc/uuid-clock so that if the time goes backwards the clock sequence counter can get bumped. This allows us to completely correctly generate time-based (version 1) UUID's according to the algorithm specified RFC 4122. Addresses-Sourceforge-Bug: #1529672 Addresses-Red-Hat-Bugzilla: #233471 Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>	2007-12-16 17:28:46 -05:00