From: Kjell Andresen (kjell.andresen@usit.uio.no)
Date: Mon Oct 20 2003 - 09:51:01 EDT
Thanks to:
Matthew Wild <M.Wild@rl.ac.uk>
LEVESQUE Bernard <blevesque@efa.lu>
"Medaglia, Chris" <cmedagli@Lifelinesys.com>
Jan Mark Holzer <jmh@hp.com>
Richardson Phil - pricha <pricha@acxiom.co.uk>
"Brusche, Johan" <johan.brusche@hp.com>
"Dr Thomas.Blinn@HP.com" <tpb@doctor.zk3.dec.com>
All agreed that the parameter was to find in /var/adm/cron/queuedefs.
Any changes will take effect after a restart of cron
(/sbin/rc3.d/s57cron stop and start)
Dr. Tom Blinn also stated:
------------------------------------------------
By the way, you may not actually want to have more than 25 jobs
active under cron at a time; that's why the default limit is set
to 25 total (across tasks from ALL the crontab files, all of the
batch and at jobs). So if cron can't run some task immediately
due to the limit, it just restarts the jobs not yet run later.
Of course, killing cron makes it forget these "non-standard"
tasks.
------------------------------------------------
The error was a cron job made to update som other machines yp database.
Solving the problem with this job also solved the error condition for my
restarted cron.
My original question was:
> Having experienced a job limit above max I just wonder
> where this value might be adjusted?
>
> From /var/adm/cron/log there is a lot of lines like this:
>
> MAXRUN (25) procs reached Fri Oct 17 22:00:00 2003
> rescheduling a cron job Fri Oct 17 22:00:00 2003
>
> I cannot find anything about this value in "man cron|tab"
>
> A restart of cron seem to have killed jobs in queue/not finished.
Regards,
Kjell Andresen Systems administrator, University of Oslo, Norway
Center for Information Technology Services and
Department of Geosciences
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:39 EDT