From owner-freebsd-net Tue Jun 27 20: 4:23 2000 Delivered-To: freebsd-net@freebsd.org Received: from pojmail01.poj.usace.army.mil (poj01.poj.usace.army.mil [155.81.110.2]) by hub.freebsd.org (Postfix) with ESMTP id DF21C37BFCF for ; Tue, 27 Jun 2000 20:04:14 -0700 (PDT) (envelope-from Barry.A.Mishler@poj.usace.army.mil) Received: by pojmail01.poj.usace.army.mil with Internet Mail Service (5.5.2650.21) id ; Wed, 28 Jun 2000 12:04:09 +0900 Message-ID: <8ACF33E983FDD31181ED009027CCC457192C1C@pojmail02.poj.usace.army.mil> From: "Mishler, Barry A POJ" To: 'Brian Reichert' Cc: freebsd-net@FreeBSD.ORG Subject: RE: suggested hack for ntpdate flags Date: Wed, 28 Jun 2000 12:04:07 +0900 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The /etc/init.d/xntpd file included with Solaris does a very similar thing with the ntp.conf file. I always thought it was a good idea. It's exactly that kind of thing that creates a good impression... making services work with minimal effort. My only question is: can it do any harm? Barry -- Barry Mishler UNIX System Administrator / Network Manager Japan Engineer District U.S. Army Corps of Engineers > -----Original Message----- > From: Brian Reichert [mailto:reichert@numachi.com] > Sent: Wednesday, June 28, 2000 4:38 AM > To: Garrett Wollman > Cc: Brian Reichert; freebsd-net@FreeBSD.ORG > Subject: Re: suggested hack for ntpdate flags > > > On Tue, Jun 27, 2000 at 03:27:13PM -0400, Garrett Wollman wrote: > > < said: > > > > > I've taken to doing this in various boxes in /etc/rc.conf: > > > ntpdate_flags="`sed -n 's/^server \(.*\)/\1/p' < /etc/ntp.conf`" > > > > > just so I don't have two lists of time servers to maintain. > > > > Hmmm. Around here, we simply call our NTP servers `ntp-0', `ntp-1', > > and `ntp-2', so there's no maintenance involved. I can see where your > > approach might help for a site which doesn't run its own NTP servers. > > I do run my own servers. Irrespective of _what_ you name your time > servers (or whether they're internal or not), with the above hack, > you only need record them once in /etc/ntpd.conf. You don't then > need to also cite them in /etc/rc.conf. > > Of course, if your site has ready mechanisms for provisioning > machines, then such things could simply be pre-configured into your > reference machine to be distributed. > > I need such a thing in that I'm responsible for preovisioning > machines in several sites; this is one of those hacks I keep carrying > around with me. > > I was volunteering it more for the masses at large, as someone new > to configuring time syncronization clients might find it useful. > > Just a suggestion anyway; I'm not going to get bent out of shape > if it's not useful to others... > > > -GAWollman > > > > -- > > Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same > > wollman@lcs.mit.edu | O Siem / The fires of freedom > > Opinions not those of| Dance in the burning flame > > MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick > > -- > Brian 'you Bastard' Reichert reichert@numachi.com > 37 Crystal Ave. #303 Daytime number: (603) 434-6842 > Derry NH 03038-1713 USA Intel architecture: the left-hand path To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message