Cron limit reached

[Eric Crosby_3]

We've run into the limit on the number of children cron can have! This is shown in the cron log as:
c queue max run limit reached

We do not have anything in the queuedefs file, so it's taking the default. Which appears to be 100 between at, batch and cron, correct?

We use cron heavily on a few of our servers and need to increase this number. If we cannot do this with HP Cron, does anyone know if Gnu cron has this same limit?

Thank you!

[Geoff Wild]

You should be ale to add a c. line in the /var/adm/cron/queuedefs file to increase the limit.

c.200j1n


man queuedefs



Rgds...Geoff

[Pete Randall]

The man page for queuedefs(4) says:

q.[njobj][nicen][nwaitw]

njob The maximum number of jobs that can be run simultaneously in that queue. Although any number can e specified here, the total number of jobs that can be run on all the queues is limited to 100.


Pete

[Pete Randall · Accepted solution]

In 11iV3 however:

njob The maximum number of jobs that can be run simultaneously in that queue. Although any number can be specified here, cron (see cron(1M)) by default limits the number of jobs that can be run on all the queues to 100. This limitation can be removed by setting the variable DISABLE_MAXJOB_LIMIT to 1 in the /etc/default/cron file.


Pete

[Armin Kunaschik]

BTW, this configuration option seems to be there at least since 11.11:

/etc/default/cron


##
# Cron allows maximum of 100 jobs to be actively running at any instance.
# Hence even if njob is set to >100 in queuedefs(4), cron daemon will still
# be able to execute maximum of 100 jobs only.
# Setting DISABLE_MAXJOB_LIMIT to 1 will set the limit for number of active
# jobs to be same as the njob defined in queuedefs(4).
# DISABLE_MAXJOB_LIMIT can be set to 1 or 0.
#
DISABLE_MAXJOB_LIMIT=0


My 2 cents,
Armin