At 09:44 AM 11/10/00 -0600, you wrote: >Does anybody have advice for keeping the time correct on a Redhat 6.2 >server? Besides going in manually and correcting it once a week like I've >been doing that is. crontab entry: 00 * * * * root /usr/sbin/ntpdate -b navobs1.wustl.edu > /dev/null (yes this is once an hour...see below) Dont forget to run "setclock" to set your RTC to the time polled from ntpdate. > >And speaking of which - does anyone know why Linux boxes seem to keep such >bad time? I had one machine here that I hadn't looked at for awhile...I >went in and checked the time on it and it was 2 years off! This is an >extreme example but my servers seem to invariable lose or gain about an >hour a week which can mess with cron jobs. My server's time drift is about 11 seconds/day which is terrible. I sync up every hour. I use a window app to code and when I save the file it saves to a samba-shared dir. The timestamp of the file is based on the clock on my windows machine. I've had several experiences where the time drifted so much in between hourly sync's that "make" complained that the time is skewed. I've noticed accurate time problems on other linux boxes i have too. Windows doesnt "seem" to have the same problem. I've not investigated but I wonder if the correlation is true... Jason > >Thanks, >Brady > >--------------------------------------------------------------------- >To unsubscribe, e-mail: tclug-list-unsubscribe at mn-linux.org >For additional commands, e-mail: tclug-list-help at mn-linux.org >