Sponsored Content
Operating Systems Linux NTPD seems to be not syncing !!! Post 94649 by Perderabo on Monday 2nd of January 2006 11:28:44 PM
Old 01-03-2006
ntp gives up completely if your clock is too far off. You should set your clock so it is as close as you can get it. Is your clock 5 seconds slow or fast? No problem. Is your clock 1001 seconds(or more) too slow or too fast? Forget ntp... it will not even try to sync the clock.

ntp needs to figure out how bad your clock is. If you reboot a lot, it has to keep starting from zero. With a drift file, it writes the drift into the file. Later when ntp restarts, it rereads the drift file. So it doesn't need to start completely over.

What server are you using? Post your whole ntp config file.
 

5 More Discussions You Might Find Interesting

1. HP-UX

Ntpd

Hello, I'm looking for assitance on setting up network time protocol on my HP-ux boxes. I have edit the .conf file accordingly. And /etc/services. But whenever I try and start the service nothing happens at all. No error message, nothing. I have a SCO box as a time server and I wish... (0 Replies)
Discussion started by: satinet
0 Replies

2. AIX

ntpd version

How to check the ntpd version of AIX 5.3 ? (3 Replies)
Discussion started by: alanlkw
3 Replies

3. Shell Programming and Scripting

Modifying the ntpd deamon script

I need to replace the line daemon ntpd $OPTIONS in the following script with daemon ntpd $OPTIONS 2>&1 > /var/log/ntpd.log & what will happen? The idea of replacing is to capture the output on the console into ntpd.log file. Will this work? ... (1 Reply)
Discussion started by: naive1977
1 Replies

4. Red Hat

ntpd -gq not working

as advised and documented, i'm trying to use the ntpd -gq instead of ntpdate. The result is that clock not set. as below. However ntpdate is working ok and had set the clock correctly this is the ntp.conf file: # cat /etc/ntp.conf logfile /var/log/ntp.log driftfile /var/lib/ntp/drift... (6 Replies)
Discussion started by: ahmad.zuhd
6 Replies

5. Debian

Ntpd slow start

on every boot, ntpd takes long time to start (after moving from dhcp to static ip). is there a way to speed it up? (1 Reply)
Discussion started by: orange47
1 Replies
CHRONY(1)							   User's Manual							 CHRONY(1)

NAME
chrony - programs for keeping computer clocks accurate SYNOPSIS
chronyc [OPTIONS] chronyd [OPTIONS] DESCRIPTION
chrony is a pair of programs for keeping computer clocks accurate. chronyd is a background (daemon) program and chronyc is a command-line interface to it. Time reference sources for chronyd can be RFC1305 NTP servers, human (via keyboard and chronyc), or the computer's real- time clock at boot time (Linux only). chronyd can determine the rate at which the computer gains or loses time and compensate for it while no external reference is present. Its use of NTP servers can be switched on and off (through chronyc) to support computers with dial- up/intermittent access to the Internet, and it can also act as an RFC1305-compatible NTP server. USAGE
chronyc is a command-line interface program which can be used to monitor chronyd's performance and to change various operating parameters whilst it is running. chronyd's main function is to obtain measurements of the true (UTC) time from one of several sources, and correct the system clock accord- ingly. It also works out the rate at which the system clock gains or loses time and uses this information to keep it accurate between mea- surements from the reference. The reference time can be derived from either Network Time Protocol (NTP) servers, reference clocks, or wristwatch-and-keyboard (via chronyc). The main source of information about the Network Time Protocol is http://www.ntp.org. It is designed so that it can work on computers which only have intermittent access to reference sources, for example computers which use a dial-up account to access the Internet or laptops. Of course, it will work well on computers with permanent connections too. In addition, on Linux it can monitor the system's real time clock performance, so the system can maintain accurate time even across reboots. Typical accuracies available between 2 machines are On an ethernet LAN : 100-200 microseconds, often much better On a V32bis dial-up modem connection : 10's of milliseconds (from one session to the next) With a good reference clock the accuracy can reach one microsecond. chronyd can also operate as an RFC1305-compatible NTP server and peer. SEE ALSO
chronyc(1), chrony(1) http://chrony.tuxfamily.org/ AUTHOR
Richard Curnow <rc@rc0.org.uk> This man-page was written by Jan Schaumann <jschauma@netmeister.org> as part of "The Missing Man Pages Project". Please see http://www.netmeister.org/misc/m2p2/index.html for details. The complete chrony documentation is supplied in texinfo format. chrony @VERSION@ @MAN_DATE@ CHRONY(1)
All times are GMT -4. The time now is 07:52 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy