Date: Fri, 12 Mar 2004 09:08:42 -0800 From: Joshua Lokken <joshua@twobirds.us> To: "Shaun T. Erickson" <ste@ste-land.com> Cc: freebsd-questions@freebsd.org Subject: Re: ntpd question Message-ID: <20040312170842.GB72483@voyager.swabbies.org> In-Reply-To: <404F324B.1000803@ste-land.com> References: <404E9061.3050805@ste-land.com> <20040310103622.GA49215@happy-idiot-talk.infracaninophile.co.uk> <404F324B.1000803@ste-land.com>
next in thread | previous in thread | raw e-mail | index | archive | help
* Shaun T. Erickson <ste@ste-land.com> [2004-03-12 08:27]: > Matthew Seaman wrote: > > >Unfortuately if you're going to run ntpd, you can't get rid of these: > >ntpd(8) will automatically bind to all interfaces on the system, and > >there are no controls within ntpd to control that. > > Darn. Thanks for the suggestions! I was already controlling access to > the port with my ipfilter firewall, and will continue to do so. I just > believe in not letting anything bind to a port, that isn't required to. > If you're just keeping one machine's clock in sync, you could try using ntpdate rather than ntpd. -- Joshua "It's hard to believe that something which is neither seen nor felt can do so much harm." "That's true. But an idea can't be seen or felt. And that's what kept the Troglytes in the mines all these centuries. A mistaken idea." -- Vanna and Kirk, "The Cloud Minders", stardate 5819.0
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040312170842.GB72483>