Hi there, the system we're currently using is an AlphaServer 2100 4/200,
which is running Digital Unix 3.0B. I discovered the problem this morning,
and it's rather puzzling.
It seems that although the cron process was still running, it was no longer
processing any jobs. When I looked at the logfile, I found these entries:
! MAXRUN (25) procs reached Fri Oct 25 07:48:00 1996
! rescheduling a cron job Fri Oct 25 07:48:00 1996
! MAXRUN (25) procs reached Fri Oct 25 07:48:00 1996
! rescheduling a cron job Fri Oct 25 07:48:00 1996
! MAXRUN (25) procs reached Fri Oct 25 07:48:00 1996
! rescheduling a cron job Fri Oct 25 07:48:00 1996
Actually, I found about 1.5MB worth of them. I searched the archives, and it
did seem that someone had this problem before with 2.0, but there was no
summary. I'd appreciate hearing from anyone who knows why this happens, or
what can be done to prevent it. I'll summarize the responses. Thanks.
--
Andrew Reynolds, Systems Administrator, Novanet Inc.
Andrew.Reynolds_at_Novanet.ns.ca
Received on Fri Oct 25 1996 - 15:33:43 NZDT