C Hamel
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).
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
John writes:
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 ?
At the minimum, you just need to add one or more time servers to connect to in your /etc/ntp.conf file, something like (use whichever public time servers that you prefer, hopefully one that is close to your machine in terms of number of network hops): server clock.isc.org server clock.llnl.gov See the comments in the file for info. You can comment out the server definitions for 127.x.x.x.
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
That's not the proper way to do it on a SuSE 9 box. To enable ntpd, just do the following as root: $ chkconfig -a xntpd $ rcxntpd start And then ntpd will be activated. It will also auto-start each time you boot. -Ti
I reinstalled and reconfigured the xntpd 4.1.1.
How can i be sure that xntpd working?
Here is the /var/log/ntp
4 Sep 13:39:07 ntpd[1820]: signal_no_reset: signal 17 had flags 4000000
4 Sep 13:39:07 ntpd[1810]: running as uid(74)/gid(65534)
euid(74)/egid(65534).
4 Sep 13:42:24 ntpd[1810]: time set 0.000000 s
4 Sep 13:42:24 ntpd[1810]: synchronisation lost
----- Original Message -----
From: "Ti Kan"
John writes:
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 ?
At the minimum, you just need to add one or more time servers to connect to in your /etc/ntp.conf file, something like (use whichever public time servers that you prefer, hopefully one that is close to your machine in terms of number of network hops):
server clock.isc.org server clock.llnl.gov
See the comments in the file for info. You can comment out the server definitions for 127.x.x.x.
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
That's not the proper way to do it on a SuSE 9 box. To enable ntpd, just do the following as root:
$ chkconfig -a xntpd $ rcxntpd start
And then ntpd will be activated. It will also auto-start each time you boot.
-Ti
-- 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
John writes:
I reinstalled and reconfigured the xntpd 4.1.1. How can i be sure that xntpd working?
Here is the /var/log/ntp
4 Sep 13:39:07 ntpd[1820]: signal_no_reset: signal 17 had flags 4000000 4 Sep 13:39:07 ntpd[1810]: running as uid(74)/gid(65534) euid(74)/egid(65534). 4 Sep 13:42:24 ntpd[1810]: time set 0.000000 s 4 Sep 13:42:24 ntpd[1810]: synchronisation lost
There are no obvious errors, but the time set 0.000000 s is a bit strange. I would expect at least a little deviation from 0 (how likely is that your current system time is accurate within 6 decimal points to actual)? At any rate, to check that your machine can talk to the time server, you can type the following command as root: $ ntpdate -u timeserver where timeserver is the fully qualified domain name or IP number of a public time server. If this doesn't produce an error then you can assume that all is well. This command actually causes your local date/time to be adjusted to match that of the time server. The /etc/init.d/xntpd startup script actually does this for you once when your system starts, and then ntpd will keep things in sync afterwards. When I do this on my machine I get: $ ntpdate -u clock.isc.org 4 Sep 03:52:44 ntpdate[15387]: adjust time server 204.152.184.72 offset -0.000295 sec -Ti
Here is the new /var/log/ntp
4 Sep 13:39:07 ntpd[1820]: signal_no_reset: signal 17 had flags 4000000
4 Sep 13:39:07 ntpd[1810]: running as uid(74)/gid(65534)
euid(74)/egid(65534).
4 Sep 13:42:24 ntpd[1810]: time set 0.000000 s
4 Sep 13:42:24 ntpd[1810]: synchronisation lost
4 Sep 13:57:36 ntpd[1810]: time reset -0.351721 s
4 Sep 13:57:36 ntpd[1810]: synchronisation lost
4 Sep 14:39:06 ntpd[1810]: can't open /var/lib/ntp/drift/ntp.drift.TEMP: No
such file or directory
How can i create the /var/lib/ntp/drift/ntp.drift
There is not such file in the /var/lib/ntp/drift/ folder.
----- Original Message -----
From: "Ti Kan"
John writes:
I reinstalled and reconfigured the xntpd 4.1.1. How can i be sure that xntpd working?
Here is the /var/log/ntp
4 Sep 13:39:07 ntpd[1820]: signal_no_reset: signal 17 had flags 4000000 4 Sep 13:39:07 ntpd[1810]: running as uid(74)/gid(65534) euid(74)/egid(65534). 4 Sep 13:42:24 ntpd[1810]: time set 0.000000 s 4 Sep 13:42:24 ntpd[1810]: synchronisation lost
There are no obvious errors, but the time set 0.000000 s is a bit strange. I would expect at least a little deviation from 0 (how likely is that your current system time is accurate within 6 decimal points to actual)? At any rate, to check that your machine can talk to the time server, you can type the following command as root:
$ ntpdate -u timeserver
where timeserver is the fully qualified domain name or IP number of a public time server. If this doesn't produce an error then you can assume that all is well. This command actually causes your local date/time to be adjusted to match that of the time server. The /etc/init.d/xntpd startup script actually does this for you once when your system starts, and then ntpd will keep things in sync afterwards.
When I do this on my machine I get:
$ ntpdate -u clock.isc.org 4 Sep 03:52:44 ntpdate[15387]: adjust time server 204.152.184.72 offset -0.000295 sec
-Ti
-- 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
* John
How can i create the /var/lib/ntp/drift/ntp.drift
There is not such file in the /var/lib/ntp/drift/ folder.
from a command line: ln -sf /var/lib/ntp/var/lib/ntp ../../ Please trim your posts. thanks, -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos
* Anders Johansson
On Sat, 2004-09-04 at 07:48 -0500, Patrick Shanahan wrote:
ln -sf /var/lib/ntp/var/lib/ntp ../../
Please read "man ln"
it's ln <target> <symlink>
ln -sf ../.. /var/lib/ntp/var/lib/ntp
Thanks, I do lots of thing backwards :^) -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos
Thanks guys.
I did what that page says
http://archive.lug.boulder.co.us/bymonth/2003.12/msg00040.html
The same as yours.
But i cannot see any ntp.drift in my /var/lib/ntp/drift/ntp.drift
Do you know why?
----- Original Message -----
From: "Patrick Shanahan"
* Anders Johansson
[09-04-04 07:55]: On Sat, 2004-09-04 at 07:48 -0500, Patrick Shanahan wrote:
ln -sf /var/lib/ntp/var/lib/ntp ../../
Please read "man ln"
it's ln <target> <symlink>
ln -sf ../.. /var/lib/ntp/var/lib/ntp
Thanks, I do lots of thing backwards :^)
-- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos
-- 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
* John
I did what that page says http://archive.lug.boulder.co.us/bymonth/2003.12/msg00040.html
The same as yours.
But i cannot see any ntp.drift in my /var/lib/ntp/drift/ntp.drift
Do you know why?
Possibly. AIUI, you only get an entry in ntp.drift when ntpd polls the master. See what entries you have in the log file: tail /var/log/ntp ie: pat@wahoo:~> tail -n 50 /var/log/ntp 3 Sep 22:20:40 ntpd[18834]: offset 0.001101 sec freq 85.840 ppm error 0.001326 poll 10 3 Sep 23:20:40 ntpd[18834]: offset -0.000411 sec freq 85.848 ppm error 0.006320 poll 10 4 Sep 00:20:41 ntpd[18834]: offset -0.000917 sec freq 85.836 ppm error 0.004229 poll 10 4 Sep 01:20:41 ntpd[18834]: offset 0.002143 sec freq 85.842 ppm error 0.002520 poll 10 4 Sep 02:20:41 ntpd[18834]: offset -0.000350 sec freq 85.841 ppm error 0.003714 poll 10 4 Sep 03:20:42 ntpd[18834]: offset -0.000578 sec freq 85.828 ppm error 0.004889 poll 10 4 Sep 04:20:42 ntpd[18834]: offset -0.000232 sec freq 85.829 ppm error 0.004048 poll 10 4 Sep 05:20:42 ntpd[18834]: offset -0.000228 sec freq 85.829 ppm error 0.005975 poll 10 4 Sep 06:20:43 ntpd[18834]: offset 0.004638 sec freq 85.808 ppm error 0.009174 poll 10 4 Sep 07:20:43 ntpd[18834]: offset 0.003784 sec freq 85.866 ppm error 0.015834 poll 10 pat@wahoo:~> l /var/lib/ntp/drift/ntp.drift -rw-r--r-- 1 root root 7 2004-09-04 07:20 /var/lib/ntp/drift/ntp.drift timestamp on the drift file compares with the last log entry. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos
Here is my /var/log/ntp
4 Sep 13:39:07 ntpd[1820]: signal_no_reset: signal 17 had flags 4000000
4 Sep 13:39:07 ntpd[1810]: running as uid(74)/gid(65534)
euid(74)/egid(65534).
4 Sep 13:42:24 ntpd[1810]: time set 0.000000 s
4 Sep 13:42:24 ntpd[1810]: synchronisation lost
4 Sep 13:57:36 ntpd[1810]: time reset -0.351721 s
4 Sep 13:57:36 ntpd[1810]: synchronisation lost
4 Sep 14:39:06 ntpd[1810]: can't open /var/lib/ntp/drift/ntp.drift.TEMP: No
such file or directory
4 Sep 15:39:05 ntpd[1810]: can't open /var/lib/ntp/drift/ntp.drift.TEMP: No
such file or directory
4 Sep 15:49:59 ntpd[1810]: ntpd exiting on signal 15
4 Sep 15:51:10 ntpd[1818]: signal_no_reset: signal 17 had flags 4000000
4 Sep 15:51:10 ntpd[1795]: running as uid(74)/gid(65534)
euid(74)/egid(65534).
4 Sep 15:54:27 ntpd[1795]: time set 0.000000 s
4 Sep 15:54:27 ntpd[1795]: synchronisation lost
4 Sep 16:09:39 ntpd[1795]: time reset -0.354726 s
4 Sep 16:09:39 ntpd[1795]: synchronisation lost
Still no ntp.drift has been created.
----- Original Message -----
From: "Patrick Shanahan"
* John
[09-04-04 08:05]: I did what that page says http://archive.lug.boulder.co.us/bymonth/2003.12/msg00040.html
The same as yours.
But i cannot see any ntp.drift in my /var/lib/ntp/drift/ntp.drift
Do you know why?
Possibly. AIUI, you only get an entry in ntp.drift when ntpd polls the master. See what entries you have in the log file: tail /var/log/ntp
ie:
pat@wahoo:~> tail -n 50 /var/log/ntp 3 Sep 22:20:40 ntpd[18834]: offset 0.001101 sec freq 85.840 ppm error 0.001326 poll 10 3 Sep 23:20:40 ntpd[18834]: offset -0.000411 sec freq 85.848 ppm error 0.006320 poll 10 4 Sep 00:20:41 ntpd[18834]: offset -0.000917 sec freq 85.836 ppm error 0.004229 poll 10 4 Sep 01:20:41 ntpd[18834]: offset 0.002143 sec freq 85.842 ppm error 0.002520 poll 10 4 Sep 02:20:41 ntpd[18834]: offset -0.000350 sec freq 85.841 ppm error 0.003714 poll 10 4 Sep 03:20:42 ntpd[18834]: offset -0.000578 sec freq 85.828 ppm error 0.004889 poll 10 4 Sep 04:20:42 ntpd[18834]: offset -0.000232 sec freq 85.829 ppm error 0.004048 poll 10 4 Sep 05:20:42 ntpd[18834]: offset -0.000228 sec freq 85.829 ppm error 0.005975 poll 10 4 Sep 06:20:43 ntpd[18834]: offset 0.004638 sec freq 85.808 ppm error 0.009174 poll 10 4 Sep 07:20:43 ntpd[18834]: offset 0.003784 sec freq 85.866 ppm error 0.015834 poll 10
pat@wahoo:~> l /var/lib/ntp/drift/ntp.drift -rw-r--r-- 1 root root 7 2004-09-04 07:20 /var/lib/ntp/drift/ntp.drift
timestamp on the drift file compares with the last log entry. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos
-- 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
* John
Here is my /var/log/ntp
4 Sep 13:39:07 ntpd[1820]: signal_no_reset: signal 17 had flags 4000000 4 Sep 13:39:07 ntpd[1810]: running as uid(74)/gid(65534) euid(74)/egid(65534). 4 Sep 13:42:24 ntpd[1810]: time set 0.000000 s 4 Sep 13:42:24 ntpd[1810]: synchronisation lost 4 Sep 13:57:36 ntpd[1810]: time reset -0.351721 s 4 Sep 13:57:36 ntpd[1810]: synchronisation lost 4 Sep 14:39:06 ntpd[1810]: can't open /var/lib/ntp/drift/ntp.drift.TEMP: No such file or directory 4 Sep 15:39:05 ntpd[1810]: can't open /var/lib/ntp/drift/ntp.drift.TEMP: No such file or directory 4 Sep 15:49:59 ntpd[1810]: ntpd exiting on signal 15 4 Sep 15:51:10 ntpd[1818]: signal_no_reset: signal 17 had flags 4000000 4 Sep 15:51:10 ntpd[1795]: running as uid(74)/gid(65534) euid(74)/egid(65534). 4 Sep 15:54:27 ntpd[1795]: time set 0.000000 s 4 Sep 15:54:27 ntpd[1795]: synchronisation lost 4 Sep 16:09:39 ntpd[1795]: time reset -0.354726 s 4 Sep 16:09:39 ntpd[1795]: synchronisation lost
Still no ntp.drift has been created.
Please trim your replies. It does not appear to be connecting to any authority. Did you enable ntp or port 123 in your firewall? ie: iptables -L|grep ntp (partial result) wahoo:~ # iptables -L |grep ntp ACCEPT udp -- navobs1.wustl.edu anywhere state NEW,RELATED,ESTABLISHED udp dpt:ntp ACCEPT udp -- darkcity.cerias.purdue.edu anywhere state NEW,RELATED,ESTABLISHED udp dpt:ntp ACCEPT udp -- 128.46.128.76 anywhere state NEW,RELATED,ESTABLISHED udp dpt:ntp ACCEPT udp -- 128.46.128.76 anywhere state NEW,RELATED,ESTABLISHED udp dpt:ntp -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos
Well,
I opened the 123 UDP port using
YAST->System->Editor for /etc/sysconfig
Files->Network->Firewall->SuSEfirewall2->FW_SERVICES_EXT_UDP='123'
Is that right?
----- Original Message -----
From: "Patrick Shanahan"
* John
[09-04-04 08:37]: Here is my /var/log/ntp
4 Sep 13:39:07 ntpd[1820]: signal_no_reset: signal 17 had flags 4000000 4 Sep 13:39:07 ntpd[1810]: running as uid(74)/gid(65534) euid(74)/egid(65534). 4 Sep 13:42:24 ntpd[1810]: time set 0.000000 s 4 Sep 13:42:24 ntpd[1810]: synchronisation lost 4 Sep 13:57:36 ntpd[1810]: time reset -0.351721 s 4 Sep 13:57:36 ntpd[1810]: synchronisation lost 4 Sep 14:39:06 ntpd[1810]: can't open /var/lib/ntp/drift/ntp.drift.TEMP: No such file or directory 4 Sep 15:39:05 ntpd[1810]: can't open /var/lib/ntp/drift/ntp.drift.TEMP: No such file or directory 4 Sep 15:49:59 ntpd[1810]: ntpd exiting on signal 15 4 Sep 15:51:10 ntpd[1818]: signal_no_reset: signal 17 had flags 4000000 4 Sep 15:51:10 ntpd[1795]: running as uid(74)/gid(65534) euid(74)/egid(65534). 4 Sep 15:54:27 ntpd[1795]: time set 0.000000 s 4 Sep 15:54:27 ntpd[1795]: synchronisation lost 4 Sep 16:09:39 ntpd[1795]: time reset -0.354726 s 4 Sep 16:09:39 ntpd[1795]: synchronisation lost
Still no ntp.drift has been created.
Please trim your replies.
It does not appear to be connecting to any authority. Did you enable ntp or port 123 in your firewall?
ie: iptables -L|grep ntp (partial result) wahoo:~ # iptables -L |grep ntp ACCEPT udp -- navobs1.wustl.edu anywhere state NEW,RELATED,ESTABLISHED udp dpt:ntp ACCEPT udp -- darkcity.cerias.purdue.edu anywhere state NEW,RELATED,ESTABLISHED udp dpt:ntp ACCEPT udp -- 128.46.128.76 anywhere state NEW,RELATED,ESTABLISHED udp dpt:ntp ACCEPT udp -- 128.46.128.76 anywhere state NEW,RELATED,ESTABLISHED udp dpt:ntp
-- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos
-- 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
On Saturday 04 September 2004 15:01, John wrote:
Thanks guys.
I did what that page says http://archive.lug.boulder.co.us/bymonth/2003.12/msg00040.html
The same as yours.
But i cannot see any ntp.drift in my /var/lib/ntp/drift/ntp.drift
Do you know why?
Yup, know bug in 9.0, had that one too. Here is the diectory that contains the with that bug solved: http://ftp.gwdg.de/pub/linux/suse/ftp.suse.com/people/pth/xntp/9.0/i386/ BTW, I know you have SuSE 9.0, in SuSE 9.1 it is a lot easier to set up the ntp servers, because there is a YaST module for that. (I just thought I should let you know ;). Cheers, Leen
On Saturday 04 September 2004 15:01, John wrote:
Thanks guys.
I did what that page says http://archive.lug.boulder.co.us/bymonth/2003.12/msg00040.html
The same as yours.
But i cannot see any ntp.drift in my /var/lib/ntp/drift/ntp.drift
Do you know why?
Yup, know bug in 9.0, had that one too. Here is the diectory that contains
with that bug solved:
http://ftp.gwdg.de/pub/linux/suse/ftp.suse.com/people/pth/xntp/9.0/i386/
BTW, I know you have SuSE 9.0, in SuSE 9.1 it is a lot easier to set up
Well,
ntp.drift was created with content.
-378.599
----- Original Message -----
From: "Leendert Meyer"
ntp servers, because there is a YaST module for that. (I just thought I should let you know ;).
Cheers,
Leen
-- 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
John wrote:
Well, ntp.drift was created with content. -378.599
John, this file is used to take track of your's clock drift rate in case of reboots - ntp.drift should stabilyze around some point in a week or so... but if you have bad quality HW, it will be changing every time www.ntp.org has a very good faq about it http://www.ntp.org/ntpfaq/NTP-s-trouble.htm - chap. 8 in special -- Marcos Lazarini
John wrote:
Well, ntp.drift was created with content. -378.599
John, this file is used to take track of your's clock drift rate in case of reboots - ntp.drift should stabilyze around some point in a week or so... but if you have bad quality HW, it will be changing every time
www.ntp.org has a very good faq about it http://www.ntp.org/ntpfaq/NTP-s-trouble.htm - chap. 8 in special
-- Marcos Lazarini I wonder if he might be happier w/the 'ntpdate' doing the leg work. I adjust
On Sunday 05 September 2004 22:36, Marcos Lazarini wrote: the clock every few hours using it. My clock seems to like to lose time even though it is a brand new box (January, this year). -- ..."Yogi" CH Namasté Yoga Studio "If music be the food of love, why can't rabbits sing?"
C Hamel wrote:
I wonder if he might be happier w/the 'ntpdate' doing the leg work. I adjust the clock every few hours using it. My clock seems to like to lose time even though it is a brand new box (January, this year).
How old the computer is, has nothing to do with it. It all depends on the accuracy of the crystal used in the clock. Some are worse than others.
I installed the xntp 4.1.1. on two SUSE 9 Pro
the first ntp.drift is -293.232 and the second is -341.845
How could i correct the ntp.drift ?
----- Original Message -----
From: "James Knott"
C Hamel wrote:
I wonder if he might be happier w/the 'ntpdate' doing the leg work. I adjust the clock every few hours using it. My clock seems to like to lose time even though it is a brand new box (January, this year).
How old the computer is, has nothing to do with it. It all depends on the accuracy of the crystal used in the clock. Some are worse than others.
-- 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
* John
I installed the xntp 4.1.1. on two SUSE 9 Pro
the first ntp.drift is -293.232 and the second is -341.845
How could i correct the ntp.drift ?
PLEASE, trim your posts. Thankyou
John Anderson's quote from the post of Marcos Lazarini told you how. Or
do you want us to read it for you?
X-Message-Number-for-archive: 206512
From: John Andersen
-----Original Message-----
From: "John"
I installed the xntp 4.1.1. on two SUSE 9 Pro
the first ntp.drift is -293.232 and the second is -341.845
How could i correct the ntp.drift ?
You can't unless you expect both PC's to have -exactly- the same clock speed, fat chance of that happening. Too many electronic parts with tolerances of +- 10%. Ken
On Monday 06 September 2004 08:30, Ken Schneider wrote:
-----Original Message----- From: "John"
To: Date: Mon, 6 Sep 2004 16:12:30 +0300 Subject: Re: [SLE] NTP & SUSE 9 I installed the xntp 4.1.1. on two SUSE 9 Pro
the first ntp.drift is -293.232 and the second is -341.845
How could i correct the ntp.drift ?
You can't unless you expect both PC's to have -exactly- the same clock speed, fat chance of that happening. Too many electronic parts with tolerances of +- 10%.
Ken
Hi, The driftfile contents are evidence that the NTP client is doing its job: Keeping the local H/W clock set to UTC standard. If the local clock didn't drift there would be no need for NTP! If you want to have no drift you will have to find a Motherboard Mfgr that supplies an atomic clock on the board. PeterB -- Using SUSE since 5.2 Loving SUSE 9.1 Pro My Blog: http://vancampen.org/blog --
Peter B Van Campen wrote:
The driftfile contents are evidence that the NTP client is doing its job: Keeping the local H/W clock set to UTC standard. If the local clock didn't drift there would be no need for NTP!
If you want to have no drift you will have to find a Motherboard Mfgr that supplies an atomic clock on the board.
Or get your own accurate time source, such as a GPS receiver. There are also short wave receivers available, that allow a computer to sync to WWV. Heathkit sold a couple several years ago, but I've seen others since then. As I recall, the Heathkit would keep a computer accurate to within 10 mS.
Ken Schneider wrote:
-----Original Message----- From: "John"
To: Date: Mon, 6 Sep 2004 16:12:30 +0300 Subject: Re: [SLE] NTP & SUSE 9 I installed the xntp 4.1.1. on two SUSE 9 Pro
the first ntp.drift is -293.232 and the second is -341.845
How could i correct the ntp.drift ?
You can't unless you expect both PC's to have -exactly- the same clock speed, fat chance of that happening. Too many electronic parts with tolerances of +- 10%.
It would be nice, if we could get a cesium atomic clock on a chip. ;-)
Running ntpd should automagically adjust for drift. As I understand it, ntpdate doesn't. I use ntp on both my desktop systems, as they're always connected to the internet. But I use ntpdate on my notebook, as it usually is turned off. I have added an item to my desktop menu, to run ntpdate. John wrote:
I installed the xntp 4.1.1. on two SUSE 9 Pro
the first ntp.drift is -293.232 and the second is -341.845
How could i correct the ntp.drift ?
----- Original Message ----- From: "James Knott"
To: Sent: Monday, September 06, 2004 4:09 PM Subject: Re: [SLE] NTP & SUSE 9 C Hamel wrote:
I wonder if he might be happier w/the 'ntpdate' doing the leg work. I
adjust
the clock every few hours using it. My clock seems to like to lose time
even
though it is a brand new box (January, this year).
How old the computer is, has nothing to do with it. It all depends on the accuracy of the crystal used in the clock. Some are worse than
others.
-- 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
On Monday 06 September 2004 05:12 am, John wrote:
I installed the xntp 4.1.1. on two SUSE 9 Pro
the first ntp.drift is -293.232 and the second is -341.845
How could i correct the ntp.drift ?
LEAVE IT ALONE. You've already stated your machines have the correct time, so just forget about the details you don't seem to understand and move on. Its working as designed. Don't touch it. Put the keyboard down!!! -- _____________________________________ John Andersen
I understood all these issues but what confused me most was the difference
of the log files between version 4.1.1. and 4.2.0-6
----- Original Message -----
From: "John Andersen"
When Suse Firewall running on nfs server (SuSE 9.1), I can't see the nfs exports from clients. I open the following ports : 111 : sunrpc 1110 : nfsd-status 1598 : picknfs 2049 : nfs 2061 : netmount 635 : rlzdbase What can I do ? Thank's
When Suse Firewall running on nfs server (SuSE 9.1), I can't see the nfs exports from clients. I open the following ports : 111 : sunrpc 1110 : nfsd-status 1598 : picknfs 2049 : nfs 2061 : netmount 635 : rlzdbase What can I do ?
Thank's I've had a few config problems w/firewall, as well. I ultimately switched to
On Monday 06 September 2004 10:08, Jean-Baptiste GIRAUDEAU wrote: portsentry & used the 'anal' settings. After that, it was a matter of getting online & starting the server --I run a small parttime file server-- and then starting portsentry. Once started, I checked the logs to see which ports were in use & eliminated them from the config file so they'd be open for business. The unathorized probes get killed & blocked. I've been using portsentry for a long time --over two or three distros-- & am very happy with it. If you would like the rpm, e-mail me privately. It's easy to set up/compile/ install. FWIW... -- ..."Yogi" CH Namasté Yoga Studio "If music be the food of love, why can't rabbits sing?"
Now my ntp.drift is -345.174
Is this a correct value?
----- Original Message -----
From: "Marcos Lazarini"
John wrote:
Well, ntp.drift was created with content. -378.599
John, this file is used to take track of your's clock drift rate in case of reboots - ntp.drift should stabilyze around some point in a week or so... but if you have bad quality HW, it will be changing every time
www.ntp.org has a very good faq about it http://www.ntp.org/ntpfaq/NTP-s-trouble.htm - chap. 8 in special
-- Marcos Lazarini
-- 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
On Sunday 05 September 2004 10:41 pm, John wrote:
Now my ntp.drift is -345.174
Is this a correct value?
Did you read the below:
John, this file is used to take track of your's clock drift rate in case of reboots - ntp.drift should stabilyze around some point in a week or so... but if you have bad quality HW, it will be changing every time
www.ntp.org has a very good faq about it http://www.ntp.org/ntpfaq/NTP-s-trouble.htm - chap. 8 in special
There is no CORRECT value. It measures how much your individual clock drifts and as such asking if the value is correct is like asking if your fingerprint is correct. -- _____________________________________ John Andersen
The "problem" is that my cleint's time has been accurate even if the
ntp.drift value is not correct.
Is that wierd or not?
I have the correct time like others machines (using ntpd).
----- Original Message -----
From: "John Andersen"
The Monday 2004-09-06 at 10:34 +0300, John wrote:
The "problem" is that my cleint's time has been accurate even if the ntp.drift value is not correct.
Is that wierd or not?
I have the correct time like others machines (using ntpd).
You are not reading what they tell you. ¿How do you tell if the drift value is correct or not? There is no such thing. If, when using the ntp daemon the time is kept accurate, then the drift value can be assumed to be correct and doing its job. The value will be different on any computer. -- Cheers, Carlos Robinson
Well, both machines have the exactly the same time and i am very happy with
that!
----- Original Message -----
From: "Carlos E. R."
The Monday 2004-09-06 at 10:34 +0300, John wrote:
The "problem" is that my cleint's time has been accurate even if the ntp.drift value is not correct.
Is that wierd or not?
I have the correct time like others machines (using ntpd).
You are not reading what they tell you. ¿How do you tell if the drift value is correct or not? There is no such thing.
If, when using the ntp daemon the time is kept accurate, then the drift value can be assumed to be correct and doing its job. The value will be different on any computer.
-- Cheers, Carlos Robinson
-- 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
participants (14)
-
Anders Johansson
-
C Hamel
-
Carlos E. R.
-
James Knott
-
Jean-Baptiste GIRAUDEAU
-
John
-
John Andersen
-
Ken Schneider
-
Leendert Meyer
-
Marcos Lazarini
-
Mark Gray
-
Patrick Shanahan
-
Peter B Van Campen
-
ti@amb.org