Description of problem:

The /etc/init.d/uuidd initscript's status command looks in a pidfile located at /var/lib/libuuid/uuidd.pid (written by the daemon) for the PID to check the status on.

Unfortunately, uuidd seems to write the PID of the original process, and not the PID resulting after the fork operation.  The result is that "/etc/init.d/uuidd status" always returns "uuidd dead but pid file exists".  This causes problems particularly with automated tools that expect the status subcommand to behave properly.

This is a bug fixed upstream at http://git.kernel.org/?p=fs/ext2/e2fsprogs.git;a=commit;h=cfa30fd554a5ec905ef1e4e3f2b1f8ba9ba8b7e5 and upstream bug tracked at http://sourceforge.net/tracker/?func=detail&aid=1893244&group_id=2406&atid=102406