Dear my friends.... I think I need xntp to make the clock of my server and my workstation be always correct. my server and the clients use SuSE 8.2. and each of them connected to the internet through router. 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"? Thank you. __________________________________ Do you Yahoo!? Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes http://hotjobs.sweepstakes.yahoo.com/signingbonus
* Prabu Subroto;
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 have to use a timeserver so your ntp clients will refer to. Hence editing the /etc/ntp.conf is required -- Togan Muftuoglu Unofficial SuSE FAQ Maintainer Please reply to the list; http://susefaq.sf.net Please don't CC me.
Dear Togan...
I can not find any place to define the timeserver.
Could you tell me I should define the timeserver?
Could you give the address and the name of the
timeservers those I can use from duisburg-germany?
Is here the place/line,
"
## Outside source of synchronized time
##
## server xx.xx.xx.xx # IP address of server
"?
Thank you very much.
--- Togan Muftuoglu
* Prabu Subroto;
on 15 Jan, 2004 wrote: 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 have to use a timeserver so your ntp clients will refer to. Hence editing the /etc/ntp.conf is required
--
Togan Muftuoglu Unofficial SuSE FAQ Maintainer Please reply to the list; http://susefaq.sf.net Please don't CC me.
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
__________________________________ Do you Yahoo!? Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes http://hotjobs.sweepstakes.yahoo.com/signingbonus
* Prabu Subroto;
Dear Togan...
I can not find any place to define the timeserver.
Could you tell me I should define the timeserver? Could you give the address and the name of the timeservers those I can use from duisburg-germany?
host de.pool.ntp.org and you have a list of ntp servers for Germany
Is here the place/line, " ## Outside source of synchronized time ## ## server xx.xx.xx.xx # IP address of server "?
The place you have found is correct here is what I have server 193.5.216.4 server 146.48.83.182 You can also use server de.pool.ntp.org however the above suits my needs as tightining my firewall and also I have the following in my /etc/ntp.conf # Set the default policy restrict default ignore # Allow queries from LocalLANS but nothing else restrict 192.168.1.0 mask 255.255.255.248 nomodify restrict 192.168.2.0 mask 255.255.255.248 nomodify # Allow localhost to do whatever it wants restrict 127.0.0.1 -- Togan Muftuoglu Unofficial SuSE FAQ Maintainer Please reply to the list; http://susefaq.sf.net Please don't CC me.
On Monday 19 January 2004 6:17 am, Prabu Subroto wrote:
Dear Togan...
I can not find any place to define the timeserver.
Could you tell me I should define the timeserver? Could you give the address and the name of the timeservers those I can use from duisburg-germany?
The best way to set up xntpd is through Yast2. Go to System / Editor for sysconfig / Network / NTP, and you'll find several relevant settings. However, you're best off to insert the timeserver IP addresses in the referenced configuration file /etc/ntp.conf. In addition to that, I found I had to twiddle the /etc/init.d entries so that xntpd actually queried the timeservers on bootup, but I no longer remember how I did that. I can say, though, that doing a recursive grep on /etc for ntp showed me where to look. As to timeservers in Germany, someone else will have to help with that. Paul Abrahams
On Monday 19 January 2004 8:30 am, Paul W. Abrahams wrote:
In addition to that, I found I had to twiddle the /etc/init.d entries so that xntpd actually queried the timeservers on bootup, but I no longer remember how I did that. I can say, though, that doing a recursive grep on /etc for ntp showed me where to look.
in /etc/sysconfig/xntp [a text file] you can set the "query on startup..." value. Afterwards, run SuSEconfig to let Suse do it's magic to write the proper config file. [you can use the "sysconfig editor" in YaST to make the change, or any other plain-text editor -- the surrounding comments are fairly comprehensive] -- Yet another Blog: http://osnut.homelinux.net
Hi everyone! I have troubles using the SuSE 9.0 on my machines because it is freezing the system with Oops of kernel with the following modules: Raid5.o, airo.o, ipv6.o, and others. A LOTS OF FAULT ONLY on runlevels 3-5, average run time 5mins. I have 3 totally different systems (1 fully scsi system k7, 1 fully IDE system p4 and a laptop p4) Does anyone has seen this problems??? David
On Thursday 15 of January 2004 16:45, Prabu Subroto wrote:
Dear my friends....
I think I need xntp to make the clock of my server and my workstation be always correct.
my server and the clients use SuSE 8.2. and each of them connected to the internet through router.
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"?
I don't use ntp daemon. ntpdate will be your friend. My scripts: ============================ /usr/local/bin/sync_clock (chmod 755): #!/bin/sh # clock synchro # launch by cron ping 194.204.159.1 -c3 -w5 | grep 'icmp_seq' >/dev/null let wynik=$? if [ $wynik -eq 0 ]; then (/usr/sbin/ntpdate ntp.task.gda.pl /sbin/hwclock --systohc ) >> /var/log/ntp_sync.log else echo No internet connection available >> /var/log/ntp_sync.log fi ==================== crontab for root (edited by crontab -e): # DO NOT EDIT THIS FILE - edit the master and reinstall. # (/tmp/crontab.26037 installed on Wed Jan 14 19:20:28 2004) # (Cron version -- $Id: crontab.c,v 2.13 1994/01/17 03:20:37 vixie Exp $) # # clock synchro 15 */3 * * * /usr/local/bin/sync_clock ===================== Cron will start every three hours (@ XX:15) time synchronization and hardware clock adjustment. Regards, -- Marek Chlopek
* 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,
The Thursday 2004-01-15 at 21:28 +0100, Gerhard den Hollander wrote:
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
Things are not so black or white. Unfortunately, xntpd needs a permanent network connection, or at least one that lasts a long enough time till the time get synchronized (even many hours) - and many people don't have it (me, for example). Therefore, xntp is not an option for us. We would need another program that gets the amount of time error from the network, just one time, and then drifts the system clock as needed without connecting again to the remote time server; ie, without further network connections. In fact, ntpdate does just that when the error is less than 0.5 seconds: | Time adjustments are made by ntpdate in one of two ways. If ntpdate | determines the clock is in error more than 0.5 second it will | simply step the time by calling the system settimeofday() routine. | If the error is less than 0.5 seconds, it will slew the time by | calling the system adjtime() routine. The latter technique is less | disruptive and more accurate when the error is small, and works | quite well when ntpdate is run by cron every hour or two. And it can be forced to slew the time even if the error is bigger than 0.5 seconds: | -B | Force the time to always be slewed using the adjtime() system | call, even if the measured offset is greater than +-128 ms. The | default is to step the time using settimeofday() if the offset | default is to step the time using settimeofday() if the offset | is greater than +-128 ms. Note that, if the offset is much | greater than +-128 ms in this case, that it can take a long | time (hours) to slew the clock to the correct value. During | this time. the host should not be used to synchronize clients. -- Cheers, Carlos Robinson
Dear my friend, Gerhard...
But I could not find any menu for xntp neither on yast
nor yast2. Could you tell me more detail to use yast2
to configure xntp using yast2?
TIC so much.
--- Gerhard den Hollander
* Marek Chlopek
(Thu, Jan 15, 2004 at 07:58:52PM +0100) 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,
== The Acoustic Motorbiker == -- __O For prosimian fun, you can bugger a lemur =`\<, To bolster your name as a pervert and schemer (=)/(=) The lemurs cry "Frink!" as a coy mating call But the hedgepod can never be buggered at all. -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
__________________________________ Do you Yahoo!? Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes http://hotjobs.sweepstakes.yahoo.com/signingbonus
* Prabu Subroto
Dear my friend, Gerhard...
But I could not find any menu for xntp neither on yast nor yast2. Could you tell me more detail to use yast2 to configure xntp using yast2?
I frgot you were using suse 8.2 read /usr/share/doc/packages/xntp-doc for full details It's all in there.
TIC so much. --- Gerhard den Hollander
wrote: * Marek Chlopek
(Thu, Jan 15, 2004 at 07:58:52PM +0100) 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
Kind regards,
Currently listening to: Vertu - AudioTrack 05
Gerhard,
The Monday 2004-01-19 at 03:20 -0800, Prabu Subroto wrote:
But I could not find any menu for xntp neither on yast nor yast2. Could you tell me more detail to use yast2 to configure xntp using yast2?
Not on suse 8.2, that's only 9.0. Use your favourite text editor. -- Cheers, Carlos Robinson
participants (8)
-
Carlos E. R.
-
David Soltero-Lugo
-
Gerhard den Hollander
-
Marek Chlopek
-
Paul W. Abrahams
-
Prabu Subroto
-
Togan Muftuoglu
-
Tom Emerson