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

20030425: clock updated on papagayo

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: 20030425: clock updated on papagayo
  • Date: Fri, 25 Apr 2003 14:45:10 -0600
>From: Unidata User Support <address@hidden>
>Organization: Unidata Program Center/UCAR
>Keywords:

Hi Clint,

We noticed that papagayo's clock was drifting (losing about a second
a day), so I logged on and setup a 'root' cron entry that runs ntpdate
once per hour.  The information about the stratum level 2 time server
that papagayo will be contacting is in the cron file, so you can see
what I did by running 'crontab -l' as 'root'.

If you don't want ntpdate running, go ahead and comment out the cron
entry.  Mike Schmidt noted that the entry shouldn't cause any problems,
and running nptdate once per hour is usually safer than running the
time server daemon xntpd continuously.

Tom

>From address@hidden Mon Apr 28 12:12:17 2003

Tom,
No problemo!  I think I used to have an entry in root's cron to do this, but
it must have disappeared at some point.

Thanks for doing that,
Clint