Richard B. Gilbert wrote:
Collins wrote:
I have been reading the ntpd man pages and other documentation at the
iesc but I have yet to find an explicit answer to the following
question.
Is it possible to configure a client so that it never attempts any
communication with a server but simply monitors a multicast group for
updates? If so how?
>
I don't believe it's possible. Ntpd needs to exchange packets even when
acting as a broadcast or multicast client. That is necessary to
establish a value for the round trip packet delay. Once the client
determines the delay, it will shut up and listen.
I believe you can do this, using a special configuration command,
(possibly 'novolley' ?) to avoid the initial exchange.
Terje
--
- <[EMAIL PROTECTED]>
"almost all programming can be viewed as an exercise in caching"
_______________________________________________
questions mailing list
[email protected]
https://lists.ntp.isc.org/mailman/listinfo/questions
