https://bugzilla.novell.com/show_bug.cgi?id=426270 User Joseph.Comfort@asu.edu added comment https://bugzilla.novell.com/show_bug.cgi?id=426270#c68 --- Comment #68 from Joseph Comfort <Joseph.Comfort@asu.edu> 2009-01-24 14:37:27 MST --- The mod in #66 does not work for me. Although marked as a duplicate, my bug #465850 may be something else. If SuSE wants to put out a fix as in #68, that is fine with me, but it does not fix my case. Here are 2 situations: 1) On my desktop, which runs essentially continuously, a reboot starts up with the time 7 hours behind (not ahead). (I am in the Phoenix time zone.) At the 'bootsplash' in the /var/log/messages file, it then jumps to the correct time. This behavior did not change with the mod in #66. Some log files are written with the wrong time information. 2) My laptop is usually off. When I turned it on, the time was 14 hours behind. I made the mod, set the correct date and time manually, and rebooted. Unlike the desktop, the time was 7 hours behind -- it was not even the correct time. Upon a second reboot, the time was again 14 hours behind. I set my clock to be for local time. The behaviors here do not happen on SuSE 10.3 or earlier versions. It is something new. I did not understand all the discussion on this issue. Are the file system people demanding a change so they can avoid the "time in the future" error messages on reboots? If so, I would prefer the messages to the new behavior. In any case, the issues here are pointing to a weakness in the development of linux (or other open source) software. There are too many independent entities, with little or no overall guiding management to ensure consistency. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.