ntpdate just killed my Xserver ! everything was back to narmal after that ! Why that ?
Hi, I can't help you but I can confirm this issue. Running ntpdate sometimes also killed my xserver. My system is runnning Suse 8.1, KDE 3.0.5, Xfree 4.2.0 on a asus a7v, athlon 800 and matrox g400. Jeroen On Sunday 30 March 2003 14:16, SuSE ASPEC GroundZero wrote:
ntpdate just killed my Xserver ! everything was back to narmal after that ! Why that ?
* Jeroen Leijen <depot@xs4all.nl> (Sun, Mar 30, 2003 at 02:28:52PM +0200)
Hi, I can't help you but I can confirm this issue. Running ntpdate sometimes also killed my xserver. My system is runnning Suse 8.1, KDE 3.0.5, Xfree 4.2.0 on a asus a7v, athlon 800 and matrox g400.
Known problem The Xserver uses the local time to sync bits and pieces. If ntpdate kicks the clock back more then a certain amount of time (a few minutes I think) it will screw up things. If ntpdate sets the clock forward your Xscreensaver will kick in. I suggest using xntpd iso ntpdate. Kind regards, -- Gerhard den Hollander Phone :+31-10.280.1515 Global IT Support manager Direct:+31-10.280.1539 Jason Geosystems BV Fax :+31-10.280.1511 (When calling please note: we are in GMT+1) gdenhollander@jasongeo.com POBox 1573 visit us at http://www.jasongeo.com 3000 BN Rotterdam JASON.......#1 in Reservoir Characterization The Netherlands This e-mail and any attachment is/are intended solely for the named addressee(s) and may contain information that is confidential and privileged. If you are not the intended recipient, we request that you do not disseminate, forward, distribute or copy this e-mail message. If you have received this e-mail message in error, please notify us immediately by telephone and destroy the original message.
Hello! Btw. I have endless problems with time settings... I'm in GMT+2 zone. Hardware clock is set to local time. In the "Select Time Zone" I've set GMT+2. In KDE in the "Adjust Date Time" I've set Europe/Minsk. Now, when I'm starting "Select Time Zone" it modifies time at start (from 16:15 to 21:16 e.g.) without asking nothing. That's really boring :( Another problem when starting system and KDE, I see time -4 hours to real... hwclock -r displays 11:29 now (I've 16:29).... Tested with hardware clock, set to UTC - the same... Can somebody help? Best regards, Andrew.
On Sun, Mar 30, 2003 at 11:30:13AM -0200, Andrew Kirilenko wrote:
Hello!
Btw. I have endless problems with time settings... I'm in GMT+2 zone. Hardware clock is set to local time.
Setting hardware clock to UTC makes life much easier. (and UTC never switches, it's absolute)
In the "Select Time Zone" I've set GMT+2.
That's correct
In KDE in the "Adjust Date Time" I've set Europe/Minsk.
This seems excessive.
Now, when I'm starting "Select Time Zone" it modifies time at start (from 16:15 to 21:16 e.g.) without asking nothing. That's really boring :(
It just does what you asked it to do :-)
Another problem when starting system and KDE, I see time -4 hours to real...
hwclock -r displays 11:29 now (I've 16:29)....
It might only mean that your hardware clock is not set to localtime.
Tested with hardware clock, set to UTC - the same...
If you set hardware clock to UTC you must also specify HWCLOCK="-u" TIMEZONE="Europe/Minsk" DEFAULT_TIMEZONE="Europe/Minsk" in /etc/sysconfig/clock Though I am no sure about Europe/Minsk. I've been using EET when I was in Minsk. Actually, I just checked a server I'm still administering over there, it uses EET and hwclock set to UTC and has no problem: HWCLOCK="-u" TIMEZONE="EET" DEFAULT_TIMEZONE="EET" date on that system reports Mon Mar 31 00:29:29 EEST 2003 right now. HTH, -Kastus
participants (5)
-
Andrew Kirilenko -
Gerhard den Hollander -
Jeroen Leijen -
Konstantin (Kastus) Shchuka -
SuSE ASPEC GroundZero