[clug] Local NTP server?
daniel at rimspace.net
Tue Dec 23 22:56:24 GMT 2008
"Chris Smart" <mail at christophersmart.com> writes:
> 2008/12/24 Daniel Pittman <daniel at rimspace.net>
> ...you would need to configure your local clock to a higher stratum than
> 16 for this to work; 13 should be fine. That way other clients will
> listen to it happily.
> Hmm.. ok. Interestingly the packet capture does show them
> communicating and comparing timestamps. I guess somewhere in there the
> client is ignoring it in the end, due to the stratum.
With a semi-current (standard) ntpd on Debian/etch I have this
# Finally, in the event that we are orphaned from any upstream clock treat the
# local clock as a very high stratum time source, more or less. This keeps
# the network consistent to a single timebase, but not to UTC, and will move
# back to UTC when upstream service is available again.
tos orphan 12
You also want to check that your platform doesn't ship a
configuration that restricts time exchange; my configuration:
# By default, exchange time with everybody, but don't allow configuration.
restrict -4 default kod notrap nomodify nopeer noquery
restrict -6 default kod notrap nomodify nopeer noquery
 I confess to being too lazy to look back through the thread and
work out which distribution it is, sorry.
More information about the linux