Digital Server 3300 hardware clock

[Dave]

Sorry for the misdirect on ntpdate...the only think I can think is that
ntp_enable must have been a valid flag at some point, 'cause I grabbed
it out of an rc.conf on one of my running servers (though admittedly one
that I installed with 5.2-RELEASE and upgraded later).  I should have
checked /etc/defaults/rc.conf before posting!

5.0-RELEASE shouldn't be used for a variety of reasons.  In my experience
it's horribly broken :>  There are a number of security issues with it as
well.  For best results, bring it up to 5.3-STABLE using the instructions
found at

http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cutting-edge.html

Though my PC164SX is on 5.3-STABLE and has been crashing lately.  But I 
think I'm having hardware issues...

Dave


On Sun, Apr 03, 2005 at 10:00:11AM -0500, Richard J. Valenta wrote:
> 
> I don't know if this question is stupid, but I don't know & I'm here to learn...  but why shouldn't Kyle be using 5.0-RELEASE?  Because there have been other releases, or because of this particular machine?
> 
> rjv
> 
> 
> -----Original Message-----
> From: owner-freebsd-alpha at freebsd.org [mailto:owner-freebsd-alpha at freebsd.org] On Behalf Of Dag-Erling Sm?rgrav
> Sent: Sunday, April 03, 2005 9:02 AM
> To: Dave
> Cc: alpha at freebsd.org
> Subject: Re: Digital Server 3300 hardware clock
> 
> Dave <friend at vortex4.net> writes:
> > On Sat, Apr 02, 2005 at 11:49:54AM -0600, Kyle S. Allender wrote:
> > > I'm having a problem with FreeBSD 5.0-RELEASE on a Digital Server 3300 (or
> > > at least I think it's a 3300).  I converted this from an NT 4 server machine
> > > almost 3 years ago and it's been running fine under 4.x/5.x for a very long
> > > time.
> 
> You shouldn't be running 5.0-RELEASE.
> 
> > > However, one issue I've continually had with this machine is that the
> > > hardware clock is off by almost 2 hours.  Ntpd can't keep the correct time
> > > because the hardware clock is too far off.
> > If you ntpdate at startup, your system clock will be set to the date you get 
> > via ntp regardless of skew.  Put the following in /etc/rc.conf:
> >
> > ntp_enable="YES"
> > ntp_flags="-b ntp.server.here"
> > ntpd_enable="YES"
> >
> > That should get you set up :>
> 
> no.  you want
> 
> ntpdate_enable="YES"
> ntpd_enable="YES"
> 
> both ntpdate and ntpd use the servers listed in /etc/ntp.conf, which
> should contain something like
> 
> server europe.pool.ntp.org
> server europe.pool.ntp.org
> server europe.pool.ntp.org
> 
> round-robin DNS will take care of the rest.
> 
> obviously, if you're not in Europe, you'll want to use a different
> pool.
> 
> the official list of public ntp servers is at
> 
> http://ntp.isc.org/bin/view/Servers/WebHome
> 
> if you just want to set the clock once, run
> 
> # ntpdate pool.ntp.org pool.ntp.org pool.ntp.org
> 
> DES
> -- 
> Dag-Erling Sm?rgrav - des at des.no
> _______________________________________________
> freebsd-alpha at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-alpha
> To unsubscribe, send any mail to "freebsd-alpha-unsubscribe at freebsd.org"
> 

-- 
Dave Cotton
friend at vortex4.net