Joachim Tingvold wrote: > On 8. mars 2010, at 03.02, Matt Nordhoff wrote: >> 4.2.6 does support only binding to specific interfaces, using a config >> option called (IIRC) "nic" or "interface". > > I'll look into that. Is it just because Debian is slow to roll out new > packages/versions, or are there any stability-issues (or whatever) with 4.2.6 > vs 4.2.4?
I don't know of any major issues with 4.2.6. Then again, I'm still using my distro's 4.2.4 package*. It's probably just because distros are often slow-moving, especially for a "set it and forget it" piece of software like NTP. I mean, tons of users will clamor for a new version of PHP or WordPress or whatever, but NTP? Most users probably forget it even exists. * Trying out a development build is on my to-do list, though. Dave Hart is working on some fun stuff, improving monlist and making the "pool" command more like manycastclient, replacing bad servers and all. >> Before that, it's possible to get ntpd to ignore traffic on certain >> interfaces, but it will still bind them. (I guess that's what that >> argument does?) > > Did that apply to sub-interfaces as well? No clue, sorry. >> What's the big problem with having it listen on a couple unnecessary >> interfaces, though? > > It's not a big problem (did I say that?). I guess I just took it for granted > that it was possible. Alright. Sorry for implying that. You're right. Most software does support listening on specific interfaces, and it's surprising that NTP didn't. (IIRC, part of the reason was that it helps prevent you from accidentally running two NTPs at once.) By the way, comp.protocols.time.ntp and the equivalent mailing list, <http://lists.ntp.org/listinfo/questions>, is a higher-traffic place to ask questions specifically about NTP itself. -- Matt Nordhoff _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
