NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
>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