Path: utzoo!mnetor!uunet!husc6!uwvax!umn-d-ub!umn-cs!ems!pwcs!elric!hawkmoon!det
From: det@hawkmoon.MN.ORG (Derek E. Terveer)
Newsgroups: comp.unix.questions
Subject: Re: cron: b queue max run limit exceeded
Message-ID: <107@hawkmoon.MN.ORG>
Date: 6 Mar 88 19:37:45 GMT
References: <584@bms-at.UUCP>
Distribution: na
Organization: One of the Eternal Champions - Richfield, Mn, USA
Lines: 22
Keywords: cron queue max run limit
Summary: edit your /usr/lib/cron/queuedefs

> The max run limit message above is often printed on our system console
> along with a rescheduling message.  This is annoying since we run applications
> on the console.  (No flames on this please - our budget is tight.)
> 
> What causes this message?

This message is caused by having too many jobs scheduled to run in queue "b".
Its a warning only.

>			     Where does cron print it?  To cron's stderr?

Not sure -- guess it must print it to /dev/console...

> To /dev/console?  Is there a way to change the limit?

Yup -- edit your /usr/lib/cron/queuedefs file so that the line that begins with
a "b" has a bigger number than "2" in front of the "j".  This will be the
number of simultaneous jobs allowed.  Alternatively, you may define more queues
(up to 26, i believe) by defining more lines similar to the ones you will find
in that file.

hope this helps,