On Sunday 09 September 2007, Tapio Sokura wrote:
> Chuck wrote:
> > i have only one server i can run ntp.org software on because of the 
multiple 
> > address binding problem. 
> 
> Why can't you let ntpd bind to all interfaces? If you really need to 
> block certain interfaces/addresses, you could just firewall them out. Or 
> rather allow NTP only on the address/interface you want and block all 
> others.

2 of these are hosts to more than 100 virtual servers and i am afraid this 
momentary binding may cause some momentary problems for the guest servers 
running on this host. i just don't like having software that wants to claim 
everything for itself instead of properly obeying orders i wish to give it. 
it has no business binding to addresses it will not be using.

although the conditions for problems appear to be momentary i am very afraid 
that somewhere down the line it may cause problems with other ip addresses in 
use. it binds then releases the virtual interfaces, however on one machine 
there are more than 350 of them so it is doing things and using resources 
that are not needed. i have it coming up with the -L option to not bind to 
virtual interfaces, but it still appears to try and then releases them.
maybe this is nothing at all, but it just bothers me that it does these 
things. what possible use could automatically binding to several hundered ip 
addresses have?



> 
> > is it possible to use openntpd for servers destined for the list as 
stratum2? 
> > that software from openntpd.org supports binding ip addresses.
> 
> openntpd is rather poor algorithmically, i.e. the quality of time served 
> is worse than with ntpd. But I guess it could be enough for pool usage.
> 

im going to have to 'sleep' on this for a while. i wanted to offer 4 different 
servers for the list, however it appears, unless i change my mind and let it 
run a while to see what happens, that only one can qualify because it would 
only have 1 interface with 1 ip and be dedicated to ntp only. quite a waste 
of hardware resources.

>    Tapio
> _______________________________________________
> timekeepers mailing list
> [email protected]
> https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
> 



-- 

Chuck




_______________________________________________
timekeepers mailing list
[email protected]
https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers

Reply via email to