I've been asked to look in on an OSR 5.0.6 site where for the last few
days, /etc/cron dies and has to be restarted.

The site has several dozen entries in assorted crontab tables; someone
installed the following as /usr/lib/cron/queuedefs:

a.4j1n
b.2j2n90w
c.1j2n60w
d.1j2n60w
e.1j2n60w
f.1j2n60w
g.1j2n60w
h.1j2n60w
i.1j2n60w
j.1j2n60w
k.1j2n60w


I've pored over the queuedefs man page, but I do not really grasp the
implications of those entries. If I turn on cron logging, I do see far
more log entries like this one:

! c queue max run limit reached Wed Mar 5 18:39:00 2008
! rescheduling a cron job Wed Mar 5 18:39:00 2008

than entries reflecting actual launching of tasks.

--
JP