I searched the archives for this problem and did not come up with
anything. We are experiencing a problem with cron deferring jobs. I am
receiving the following in the /usr/adm/cron/log:
! MAXRUN (25) procs reached Wed Nov 15 04:34:00 1995
! rescheduling a cron job Wed Nov 15 04:34:00 1995
! MAXRUN (25) procs reached Wed Nov 15 04:34:00 1995
! rescheduling a cron job Wed Nov 15 04:34:00 1995
! MAXRUN (25) procs reached Wed Nov 15 04:35:00 1995
! rescheduling a cron job Wed Nov 15 04:35:00 1995
! MAXRUN (25) procs reached Wed Nov 15 04:35:00 1995
! rescheduling a cron job Wed Nov 15 04:35:00 1995
! MAXRUN (25) procs reached Wed Nov 15 04:36:00 1995
! rescheduling a cron job Wed Nov 15 04:36:00 1995
After looking around in this file, I realized that we have been seeing this
message back under 2.0, just after putting this machine into production
(we added several cron jobs at that point). Many cron jobs are simply not
being run, without any errors (besides the one above) evident. I have
searched the kernel files for a tuneable parameter called MAXRUN but
did not find anything. SYSLOG reports nothing.
Does anyone know what is causing this, and if there is a patch available
(and the ID)? This is causing our backup to not run, which is needless to
say a critical problem.
I will summarize.
Bob
haskins_at_myapc.com
Received on Wed Nov 15 1995 - 18:49:35 NZDT