Description of problem: The new glibc (or something else made available to up2date between 4/5 and 4/12) corrupts time-of-day logging during boot. It appears timezone information is corrupted from when sshd starts and some point later in booting. Version-Release number of selected component (if applicable): glibc-2.3.2-4.80.6 How reproducible: 100% of the two times I rebooted since updating Steps to Reproduce: 0. Have system clock set to use UTC. 1. run up2date to get the latest RPMs. 2. reboot. 3. Look at times in /var/log/boot.log. They will jump forward several hours just after sshd starts. Then, they will jump back to where they are supposed to be later in the boot sequence. Actual results: Times logged in /var/log/boot.log and /var/log/messages jump ahead several hours just after sshd starts and jump back later in the sequence. Expected results: Times logged should be reasonably monotonic. Additional info:
I never saw anything like this and apparently nobody else did. Can you reproduce this on a freshly installed system without local modifications? And especially with RHL9?
No reply in more than 5 months. I'm closing this as WORKSFORME.