Evan, > I am having a problem with my LDM client/server and I would really > appreciate it if you could help me out. > > Cron doesn't run ldmadmin newlog and scour. Manually those command work > fine and files configured to scour.conf are deleted without problems. > Cron log /var/log/cron indicates that task is perfomed, but nothing > happens. Please see attached log file. > > Many thanks! > Evan > > > address@hidden log]# more cron > Feb 10 04:22:01 vsoldm crond: (root) CMD (run-parts /etc/cron.weekly) > Feb 10 04:22:01 vsoldm anacron: Updated timestamp for job `cron.weekly' > to > 2008-02-10 > Feb 10 05:01:01 vsoldm crond: (root) CMD (run-parts /etc/cron.hourly) > Feb 10 06:01:01 vsoldm crond: (root) CMD (run-parts /etc/cron.hourly) > Feb 10 07:00:01 vsoldm crond: (root) CMD (root /home/ldm/bin/ldmadmin > sco > ur) > Feb 10 07:01:01 vsoldm crond: (root) CMD (run-parts /etc/cron.hourly) ... I'm not sure how to interpret the "cron" log file. Would you please log onto the system as the LDM user and send me the output of the commands: uname -a crontab -l Regards, Steve Emmerson Ticket Details =================== Ticket ID: BQO-747711 Department: Support LDM Priority: Normal Status: On Hold
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.