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

20030704: UGa upgrading to latest LDM-6 (cont.)

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: 20030704: UGa upgrading to latest LDM-6 (cont.)
  • Date: Fri, 04 Jul 2003 11:43:45 -0600
>From: "Thomas L. Mote" <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200307031521.h63FLfLd024002 LDM-6 rtstats

Tom,

>You are correct... we were updating the time twice
>per day. The departmental tech staff here insists I
>use an "rdate -s" command to the campus time server in
>the crontab rather than ntp.

This will set the time like ntpdate which is also run out of
cron.  Given this, all you need to do is increase the frequency
with which this is run from twice per day to once per hour.

>I'm not sure why;
>maybe a firewall issue. I may ask them about this
>issue again. Anyway, I changed the crontab
>so that it runs hourly.

The ntp daemon has known security issues.  Running ntpdate, and
probably rdate out of cron do not.  We are all for maximum security,
so we recommend ntpdate to sites that do not want to have to deal
with keeping on top of xntpd security.

Increasing the frequence with which rdate is run should set the
clock nicely.  I can't imagine that your departmental technical
staff would object to it running once per hour instead of twice
per day.

Tom