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#c76
Joseph Comfort changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |ASSIGNED
Info Provider|pbaudis@novell.com |
--- Comment #76 from Joseph Comfort 2009-02-07 12:51:01 MST ---
3 computers:
1) Desktop, openSuSE 10.3
2) Desktop, openSuSE 11.1
3) Laptop, openSuSE 11.1
Facts:
Computer 1 has /etc/localtime as a real file (copy of /usr/share...
Computers 2 & 3 have /etc/localtime as a soft link to
..//usr/share/zoneinfo/America/Phoenix [note //]
Computers 1 and 2 do not have /etc/adjtime
Computer 3 has /etc/adjtime [a comment below]
None of the computers have /etc/UTC
/ and /usr are separate partitions (along with some others).
My laptop had been off a few days. When started up, the log file showed the
time as 7 hours earlier (behind the actual time), and it never corrected. I
manually reset the time. The /etc/adjtime file was created at that time, and
the /etc/localtime also showed that time.
A change that fixes my problems:
Instead of having a soft link, I copied /usr/share/zoneinfo/America/Phoenix to
/etc/localtime. Now, on boot and all reboots, the time is continuous and
correct in /var/log/messages and in the display clock. (!)
Of course, the hard copy is not the way things are installed in 11.1, although
it is that way in 10.3. So the problem seems to be the install procedures.
The rpms, or whatever, must also ensure that the /etc/localtime file is a hard
copy whenever an update is installed.
If the system people want to patch and update boot.clock, that would be fine.
But an update to make /etc/localtime a real file is also needed, and should be
pushed out very soon. Then 11.1 will behave correctly as does 10.3.
--
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.