Xref: utzoo comp.unix.xenix:8032 comp.unix.questions:16955 Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cwjcc!hal!ncoast!allbery From: allbery@NCoast.ORG (Brandon S. Allbery) Newsgroups: comp.unix.xenix,comp.unix.questions Subject: Re: b queue max run limit reached Message-ID: <1989Oct12.234742.16537@NCoast.ORG> Date: 12 Oct 89 23:47:42 GMT References: <1006@mgse.UUCP> Reply-To: allbery@ncoast.ORG (Brandon S. Allbery) Followup-To: comp.unix.xenix Organization: North Coast Public Access UN*X, Cleveland, OH Lines: 56 As quoted from <1006@mgse.UUCP> by marks@mgse.UUCP (Mark Seiffert): +--------------- | I am batching some stuff up to be done and i keep getting the message | | ! b queue max run limit reached Fri Oct 6 15:11:14 CDT 1989 | ! rescheduling at job Fri Oct 6 15:11:14 CDT 1989 | | These messages keep appearing on tty01 and are annoying. Right now there | are two at jobs running and two more pending. Is there anyway to increase | the number of batched jobs? Is there any way to stop the message on the | console? I don't mind that the job is being rescheduled, it is just a little | hard to use tty01. +--------------- It looks like cron opens /dev/console to write its messages; in other words, you're stuck with them. (Change /dev/console and you get an unusable system, except that the next reboot will put it back the way it was.) You might use a binary patcher or Gnumacs to edit /etc/cron and change /dev/console to something else, though. Queue limits: Check out /usr/lib/cron/queuedefs. Here's ours (standard): a.4j1n b.2j2n90w This is in the format ".", where is one or more of: j number of concurrent jobs n amount to "nice" jobs (see nice(C)) w timw to wait between jobs (? -- I think) There may be other options, but queuedefs isn't documented and we don't have a source license. Anyway, just up the number before the "j" on the "b" line. In case you're interested, there are three standard queues: a standard "at" queue b "batch" queue ("batch" is just "at -qb") c "cron" queue -- don't touch it!!! Other queues can be created and used; "at -qX" places an "at" job on queue X. As far as I can tell, you can specify a time to execute unless the "w" option is on the queue, in which case "at" sets the time itself as seconds from submission time. This facility makes it easy to create multiple "at-like" and "batch-like" queues, with different priorities, etc. Pity it's not documented. (BTW, this seems to be the standard SVR2 cron, so anyone with SVR2 or later can make use of this feature.) ++Brandon -- Brandon S. Allbery, moderator of comp.sources.misc allbery@NCoast.ORG uunet!hal.cwru.edu!ncoast!allbery ncoast!allbery@hal.cwru.edu bsa@telotech.uucp, 161-7070 BALLBERY (MCI), ALLBERY (Delphi), B.ALLBERY (GEnie) Is that enough addresses for you? no? then: allbery@uunet.UU.NET (c.s.misc)