| Re: [chrony-dev] Running chronyd without syncing system clock |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
Op 22/02/2012 om 23:07:51 +0000, schreef Ed W:
> >In our setup we do not like to pin a service to a specific piece of
> >hardware. If, for some reason, a service should run elsewhere we just
> >stop it en start it elsewhere. bind() make is invisible for the outside
> >to see and firewalls do not need to know about it either. This is what
> >we do for all our services, except ... ntp
>
> I do something similar, but it later occurred to me that it serves
> no useful purpose to put two ntp servers on a single clocked
> machine?
This is exactly why I want to separate the systemclock sync from the
networkservice so that each instance serves a specific purpose.
> My solution was to pin NTP instances to hardware and if
> they go down then they go down (do you care?) - if you do care then
> why not make the failover system be something which pushes IPs to
> working instances (so some individual instances might appear to be
> two servers) rather than instances which know their IPs..?
>
In that case I cannot bind them to a specific IP adress which is needed
to be transparant for firewalls in and outside my network.
> The point is that you don't seem to gain anything by running two
> instances of ntp on a single physical machine? (Just the appearance
> that instances are doing something?)
>
> What do you think?
>
I disagree :)
--
Leo Baltus, internetbeheerder /\
NPO ICT Internet Services /NPO/\
Sumatralaan 45, 1217 GP Hilversum, Filmcentrum, west \ /\/
beheer@xxxxxxxxx, 035-6773555 \/
--
To unsubscribe email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "unsubscribe" in the subject.
For help email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.