Well,
I opened the 123 UDP port using
YAST->System->Editor for /etc/sysconfig
Files->Network->Firewall->SuSEfirewall2->FW_SERVICES_EXT_UDP='123'
Now what is the appropriate configuration of /etc/ntp.conf ?
I start the xntpd using the following line in the boot.local
/usr/sbin/ntpd -p /var/lib/ntp/var/run/ntp/ntpd.pid -u ntp:nogroup -i
/var/lib/ntp -c /etc/ntp.conf -c /etc/ntp.conf
What else should i do to put ntp into work?
----- Original Message -----
From: "Mark Gray"
C Hamel
writes: On Friday 03 September 2004 11:54, John wrote:
It's SuSEFirewall(what about in that case?)
Is xntpd-4.1.1 bug free or not?
If you're looking for a good clock-setting engine you can run ntpdate from cron to set your clock. It is a one-shot deal, and can be run once per day or whatever is comfortable for your situation. Example follows: ==== #!/bin/sh # # Is internet connection active? result=$(cinternet -i ppp0 -s | grep connect) #Test to see if the value is not NULL if [ -n "$result" ] then #Yes... Update hdwe clock ntpdate -b -u 132.246.168.148 #open server IP #No... so just exit else exit 0 fi ==== Works like a champ. Thanks to a couple other suse-linux-e members who dropped the ideas on this list. :-)
It is good to augment ntpdate with adjtimex. Once you determine a good frequency adjustment to use, you can stick a call to adjtimex with that frequency adjustment in your /etc/rc.d/boot.local and have your time very accurate in between calls to ntpdate as well. My firewall keeps time accurate to better than .05 seconds a day using adjtimex, and without it, it gains 2 seconds a day.
(See man adjtimex).
-- 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