Re: Time Issue
- From: houghi <houghi@xxxxxxxxxxxxxxxxxx>
- Date: Sun, 17 Sep 2006 08:38:33 +0200
Andreas wrote:
I had the same kind of problem here, it happened only sometimes and only
when I restarted the pc, never the first time after I switched it on. The
clock was off by 7 hours, and when I tried to correct if with yast, it had
set itself as soon as the window opened.
Ah. And that is clearly related to you HW time. From your header:
Date: Sat, 16 Sep 2006 22:21:35 -0700
See, if people explain how much the time difference is, it is a lot
easier to understand where the problem comes from and where it thus
should be repaired.
After changing the bootscript /etc/init.d/boot.clock the bug did not
reoccur. Here is the diff for the Suse 10.1 bootscript. I simply added a
short delay before the system time was set:
I asume that this will delay the booting of the system a bit. About a
second and a half.
--- boot.clock~ 2006-04-28 04:52:14.000000000 -0700
+++ boot.clock 2006-04-29 14:59:14.000000000 -0700
@@ -79,6 +79,7 @@
fi
/sbin/hwclock --adjust $HWCLOCK
rc_status
+ sleep 1.5
/sbin/hwclock --hctosys $HWCLOCK
rc_status
else
For those who don't understand what the above means, here a 'human
readable' translation.
1) open a terminal
2) become root with `sux -`
3) open /etc/init.d/boot.clock with your favorite editor
4) Look for the line "/sbin/hwclock --adjust $HWCLOCK"
6) Put "sleep 1.5" in the line just before it, no quotes
7) Save the file
8) Exit as root
9) close the terminal
So there. Oh and step 5 is : drink beer.
houghi
--
If God doesn't destroy Hollywood Boulevard, he owes Sodom and
Gomorrah an apology.
.
- Follow-Ups:
- Re: Time Issue
- From: Andreas
- Re: Time Issue
- References:
- Time Issue
- From: Clois Beckwith
- Re: Time Issue
- From: Andreas
- Time Issue
- Prev by Date: USB KVM switch problem
- Next by Date: Suse equivalent for BNR2
- Previous by thread: Re: Time Issue
- Next by thread: Re: Time Issue
- Index(es):
Relevant Pages
|