Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

ntpd on Red Hat



Thanks Matt,
It appears that port 23 is blocked on our box. Our network should be wide 
open, but if it is blocked by NEDV, that's ok. A manual tweak once a week 
would be sufficient. 
On 4 Apr 2002 at 15:22, Matthew J. Brodeur wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On Thu, 4 Apr 2002, Jerry Feldman wrote:
> 
> > The BLU server tends to drift. 
> > I have ntpd running with a few time servers set up in ntp.conf. It appears 
> > that ntpd is essentially a nop. It is running, but does not appear to 
> > adjust the time based on the servers. I have the same servers set up for my 
> > home system (SuSE running xntpd), which does appear to time synch 
> > successfully. 
> 
>    Although it sounds like a network problem, I'd like to point out the 
> 'step-tickers' file.  If you create the file:
> /etc/ntp/step-tickers
>    The ntpd startup script will try use ntpdate to sync to the listed 
> servers before actually starting ntpd.  The format of the file is just a 
> hostname or address on each line, with #-style comments allowed.
> 
> 
> > I tried running ntpdate on several servers listed in the public ntp web 
> >
> > I suppose that running ntpdate once daily would be more than sufficient.
> 
>    I'd recommend against using just ntpdate to set the clock.  For one, 
> if ntpdate works, ntpd should work also, so you might as well use it.  The 
> use of ntpdate seems to annoy certain people as well.  I don't remember 
> the details, but it's generally regarded as a Bad Thing, and there has 
> been talk of removing it from future releases.
> 
>    If it turns out that the ntp ports are blocked on that network you can 
> still get decent accuracy by twiddling the kernel time settings with 
> tickadj/adjtimex.  It's tedious, but I have personally managed to bring an 
> Alpha from more than +30s/day to under a second a week after only a few 
> days of adjustments.  
> 
> 
> - -- 
>      -Matt
> 
> Do not attribute to poor spelling that which is actually poor typing... 
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.6 (GNU/Linux)
> Comment: For info see http://www.gnupg.org
> 
> iD8DBQE8rLYhc8/WFSz+GKMRAqe4AJ0e3DltUcZVPmbvsjQDScSm9whsAACfQGnl
> QeFHzyBnG1X55IsrZEI29vI=
> =11Ic
> -----END PGP SIGNATURE-----
> 
> _______________________________________________
> Discuss mailing list
> Discuss at blu.org
> http://www.blu.org/mailman/listinfo/discuss


--
Jerry Feldman <gaf at blu.org>
Associate Director
Boston Linux and Unix user group
http://www.blu.org PGP key id:C5061EA9
PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9





BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org