Thanks to David Hull, Dela Acolatse, Jeffrey Hummel, Dennis Sylvester, and
Rick Hummers for their responses. It turns out there was a process that is
ran from the cron that is schedualed every hour. It was a script file that
looks for a lock file and if it is not there it will spawn another process.
It turns out that we had 25 of those running and after stopping all 25
processes then cron activity returned to normal. Suggestions included
upping max processes that can be ran at one time (default is 25).
Thanks again,
Chris Bryant
Unix Administrator
Dollar Rent A Car
(918) 669-3213
-----Original Message-----
From: Chris Bryant [mailto:cbryant_at_dollar.com]
Sent: Monday, December 03, 2001 1:40 PM
To: Tru64 Unix (E-mail)
Subject: Cron running but no schedualed jobs run.
Admins,
I have a alpha 4100 running tru64 5.1 pk 3. We are seeing strange
behavior from cron. The cron process is running yet no crontab entries will
run. Any ideas?
TIA,
Chris Bryant
Unix Administrator
Dollar Rent A Car
(918) 669-3213
Received on Mon Dec 03 2001 - 20:22:39 NZDT