Description of problem: Rebooting a server causes entries in /dev to be created with a timestamp set in the future e.g. /dev/null. [root@eng-syd-022 sysconfig]# ls -l --full-time /dev/null crw-rw-rw- 1 root root 1, 3 2007-06-07 23:07:19.758820480 +1000 /dev/null [root@eng-syd-022 sysconfig]# date Thu Jun 7 12:40:58 EST 2007 [root@eng-syd-022 sysconfig]# hwclock Thu 07 Jun 2007 12:41:09 PM EST -0.899664 seconds Version-Release number of selected component (if applicable): [root@eng-syd-022 sysconfig]# rpm -q udev udev-039-10.15.EL4 How reproducible: Set the timezone to Australia/Sydney, ensure the hardware clock is set to localtime .e.g. [root@eng-syd-022 sysconfig]# more /etc/sysconfig/clock ZONE="Australia/Sydney" UTC=false ARC=false Steps to Reproduce: 1. Reboot server 2. Compare current time with timestamp on /dev/null and friends. 3. timestamp should be in the future. Actual results: root@eng-syd-022 sysconfig]# ls -l --full-time /dev/null crw-rw-rw- 1 root root 1, 3 2007-06-07 23:07:19.758820480 +1000 /dev/null Expected results: A timestamp for /dev/null that is NOT in the future! Additional info: This is completely repeatable. I have created a vmware instance, removed /dev/null just prior to a reboot and udev still creates /dev/null with a timestamp in the future.
Created attachment 156421 [details] list of devices and timestamps in /dev created around Thu Jun 7 12:40:58 EST 2007
This sounds like a duplicate of bug 230997, fixed in a later initscripts build for RHEL 4. *** This bug has been marked as a duplicate of 230997 ***