* Marek Chlopek
I installed the xntp from the cd, and start the service on runlevel editor tool (xntpd) and do "rcxntpd start".
either on the server and client I did the same.
Is it enough to make the xntp keep the clock of each machine be always correct? do I have to edit/configure "/etc/ntp.conf"?
You need to use yast to configure ntp (initial server, peers &c) You can also edit ntp.conf directly, but the yast way is easier.
I don't use ntp daemon. ntpdate will be your friend. No it's not.
Cron will start every three hours (@ XX:15) time synchronization and hardware clock adjustment.
If you do this, ntpdate will forcefully change your system clock to the
right time. However X (and most notably motif) can get quite confused in
this case.
Im not sure of the exact casue, but I think it's realted to the following:\
X is event driven, each event has a timestamp associated with it.
If ntpdate changes the systemclock back, it might be that events that came
later have an earlier timestamp, consfusing the Xserver.
In my case, this showed up as Motif pulldown menus no longer responding
(but keeping the mouse cursor locked) untill you used the cursor keys/enter
key to leave the menu.
And X is only the most visible effect. many other apps don;t like it if the
time changes more than a few seconds.
xntpd handles this scenario gracefully by drifting the clokc (slowing it
down or speeding it up) until it gets in sync with the real time clock
In other words.
xntpd is your friend
ntpdate is your foe
read /usr/share/doc/packages/xntp-doc for full details
Currently listening to: 12 - save me
Gerhard,