Hide Forgot
Description of problem: The uuidd service does not create the corresponding (corect) pid file. Version-Release number of selected component (if applicable): [root@rstcenter ~]# cat /etc/*release CentOS release 5.7 (Final) [root@rstcenter ~]# rpm -qa e2fsprogs e2fsprogs-1.39-33.el5 [root@rstcenter ~]# rpm -qa uuidd uuidd-1.39-33.el5 Steps to Reproduce: 1.Start the uuidd service or run the binary 2.Check the pid file created 3.Compare the pid file with the associated pid of the binary Actual results: [root@rstcenter ~]# ps -efa |grep uuidd root 4560 1 0 07:49 ? 00:00:00 /usr/sbin/uuidd [root@rstcenter ~]# cat /var/lib/libuuid/uuidd.pid 4559 Expected results: 4560 (as the associated pid) Additional info: Same happens even if you run the service uuidd start command or directly /usr/sbin/uuidd, so it is not a service problem. Conclusion: The uuidd binary creates a pid file with 1 integer less than the original pid associated to the process
Sorry for the misleading post. The bug was fixed in version: E2fsprogs 1.40.7 Fix uuidd so that it creates the pid file with the correct pid number. (Addresses Sourceforge Bug: #1893244)
Should be fixed in e2fsprogs-1.39-34.el5, available in RHEL5.9. *** This bug has been marked as a duplicate of bug 707433 ***