I don't get what is going on. By default ntp should be continuously keeping the clock synced. In order for ntp to only run once it has to started with a command line arg that specifically makes it set the clock and exit. In other words for this to happen the default configuration for ntp has to be incorrect if the intent is to keep the clock synced with one or more external servers on an ongoing basis.
Also it appears that the configuration only allows for selecting one IP address for the ntp server. As a general rule using only one time server is a BAD idea since there is no way for ntp to detect if the server is keeping good time. Most ntp experts recommend using AT LEAST 4 servers since this will allow for two failures before ntp can no longer detect "bad tickers".
Related to this is it possible to hand configure the ntp server so that it behaves the way it should? IE. can I hand configure it using the /etc/ntp configuration file like I would on a normal Linux box? Is there a way to override the startup arguments?
Also is PPS and the kernel consumer configured in the kernel so that a local reference clock (like a GPS with a PPS signal) can be used?
Joined: 04 Oct 2007 Posts: 1258 Location: Ohio USA
Posted: Mon Dec 19, 2011 19:18 Post subject:
hvengel wrote:
I don't get what is going on. By default ntp should be continuously keeping the clock synced. In order for ntp to only run once it has to started with a command line arg that specifically makes it set the clock and exit. In other words for this to happen the default configuration for ntp has to be incorrect if the intent is to keep the clock synced with one or more external servers on an ongoing basis.
Also it appears that the configuration only allows for selecting one IP address for the ntp server. As a general rule using only one time server is a BAD idea since there is no way for ntp to detect if the server is keeping good time. Most ntp experts recommend using AT LEAST 4 servers since this will allow for two failures before ntp can no longer detect "bad tickers".
Related to this is it possible to hand configure the ntp server so that it behaves the way it should? IE. can I hand configure it using the /etc/ntp configuration file like I would on a normal Linux box? Is there a way to override the startup arguments?
Also is PPS and the kernel consumer configured in the kernel so that a local reference clock (like a GPS with a PPS signal) can be used?
Usage: ntpclient [options]
options:
-c count stop after count time measurements (default 0 means go forever)
-d print diagnostics (feature can be disabled at compile time)
-g goodness causes ntpclient to stop after getting a result more accurate
than goodness (microseconds, default 0 means go forever)
-h hostname (mandatory) NTP server host, against which to measure system time
-i interval check time every interval seconds (default 600)
-l attempt to lock local clock to server using adjtimex(2)
-p port local NTP client UDP port (default 0 means "any available")
-r replay analysis code based on stdin
-s simple clock set (implies -c 1)
Also, this ntpclient is not the same as the ntp daemon you see on your linux box that reads from an /etc/ntp.conf configuration file. _________________ (05/02/17) std - 31924
Linksys WRT400N
Buffalo WHR-G300N
Yes I see that that this is running ntpclient and not ntpd. Is there a way to setup the ntp daemon instead of the ntpclient?
I see that ntpclient can be run as a daemon. Why not set this up as an option for dd-wrt users? Also the Linux kernel is now much more advanced in it's time handling (many improvements starting with 2.6.26) and the new kernel time keeping code is designed with using the ntp daemon in mind.
Joined: 04 Oct 2007 Posts: 1258 Location: Ohio USA
Posted: Mon Dec 19, 2011 23:02 Post subject:
hvengel wrote:
Yes I see that that this is running ntpclient and not ntpd. Is there a way to setup the ntp daemon instead of the ntpclient?
I see that ntpclient can be run as a daemon. Why not set this up as an option for dd-wrt users? Also the Linux kernel is now much more advanced in it's time handling (many improvements starting with 2.6.26) and the new kernel time keeping code is designed with using the ntp daemon in mind.