Brett,
Not a good idea to configure more than one local clock in the network.
Over time each machine will diverge from the other. The new orphan mode
is designed for configurations like yours, but should be considered beta
until more experience is gained. Meanwhile, elevate the stratum of on
machine or the other so that the machines won't fight each other.
Dave
[EMAIL PROTECTED] wrote:
Hi,
We have 2 ES40 Alpha servers running Tru64 Unix and they are configured
as peers using their local clocks. We configred them this way for
redundacny, so that if one died the network would still have a time
server.
The ntp.conf files are configured as such:
terrance's ntp.conf:
peer phillip
peer 127.127.1.1
phillip's ntp.conf:
peer terrance
peer 127.127.1.1
Currently they have been up and running for about 14 months and the
clocks are now about 30 minutes slow.
Any ideas how I can better configure these 2 servers to keep the clocks
no time. Also, whats the best method to update the time (I was just
going to use date to set the time)
Another thing is these servers have no access to the internet at all.
Thanks in advance,
Brett.
_______________________________________________
questions mailing list
[email protected]
https://lists.ntp.isc.org/mailman/listinfo/questions
