Gilbert,
I'm getting this message emailed to me from my root account on every
machine I have LDM 6.8.0 on. Running the ldmadmin newlog command
manually yields no issues.
*******************************************************************************
Gilbert Sebenste
********
(My opinions only!)
******
Staff Meteorologist, Northern Illinois University
****
E-mail:
sebenste@xxxxxxxxxxxxxxxxxxxxx ***
web: http://weather.admin.niu.edu **
*******************************************************************************
---------- Forwarded message ----------
Date: Sat, 1 Aug 2009 01:04:01 -0500 (CDT)
From: Cron Daemon <root@xxxxxxxxxxxxxxxxxxxxxx>
Subject: Cron <ldm@XXXXXXXX> /home/ldm/bin/ldmadmin newlog
Couldn't invoke the ntpdate(1) utility, "ntpdate": No such file
or directory. Set the value of the variable "$ntpdate" in the
configuration-file, /home/ldm/etc/ldmadmin-pl.conf, to the pathname of
the ntpdate(1) utility.
You should either fix the problem (recommended) or disable time-checking
by setting the variable "$check_time" to 0 in the configuration-file,
/home/ldm/etc/ldmadmin-pl.conf, (not recommended).
The ldmadmin(1) script can't find the ntpdate(1) utility --- probably
because "/usr/sbin" isn't in the PATH environment variable when
ldmadmin(1) is run by cron(8). I suspect that the LDM user sets the
PATH environment variable in their ".bash_profile" or ".login"
profile-file rather than in their ".bashrc" or ".cshrc" profile-file,
which is why it works manually but not when executed by cron(8). Move
the setting of PATH and things should work.
Alternatively, set the variable $ntpdate in the ldmadmin(1)
configuration-file (etc/ldmadmin-pl.conf) to the absolute pathname of
the utility.
_______________________________________________
ldm-users mailing list
ldm-users@xxxxxxxxxxxxxxxx
For list information or to unsubscribe, visit:
http://www.unidata.ucar.edu/mailing_lists/
Regards,
Steve Emmerson
