[ntp:questions] Synchronizing contrived time
Amit Dor-Shifer
amit.dor.shifer at gmail.com
Mon Mar 10 10:51:39 UTC 2014
Thanks guys.
However, I can't get ntpd to process the above.
amit at zelda:~/test_ntpd$ ps -ef |grep ntpd
amit 2066 1868 0 21:39 pts/2 00:00:00 grep --color=auto ntpd
amit at zelda:~/test_ntpd$ cat ~/test_ntpd/ntp.conf
server 127.127.1.0 minpoll 4 maxpoll 4
amit at zelda:~/test_ntpd$ /usr/sbin/openntpd -f ~/test_ntpd/ntp.conf
/home/amit/test_ntpd/ntp.conf:1: syntax error
amit at zelda:~/test_ntpd$ dpkg -S /usr/sbin/openntpd
openntpd: /usr/sbin/openntpd
amit at zelda:~/test_ntpd$ dpkg -l openntpd
Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Description
+++-==============-==============-============================================
ii openntpd 3.9p1+debian-9 OpenBSD NTP daemon
Amit
On Mon, Mar 10, 2014 at 8:19 PM, David Woolley <
david at ex.djwhome.demon.invalid> wrote:
> On 10/03/14 08:09, mike cook wrote:
>
>> server 127.127.1.0 minpoll 4 maxpoll 4
>>
>
> Best practice with an undisciplined local clock is to also set the stratum
> to the largest number that still works. That prevents people accidentally
> using your bogus time from one of your clients.
>
> One other thing, the bogus time still needs to advance smoothly at 1
> second per second within about 100ppm of static error and with very low
> jitter, and with no abrupt steps. ntpd is not intended to handle unnatural
> time steps well.
>
>
> _______________________________________________
> questions mailing list
> questions at lists.ntp.org
> http://lists.ntp.org/listinfo/questions
>
More information about the questions
mailing list