🚀 go-pugleaf

#> First, a little something about the SysV cron.  
#> This is an impressive piece of work!  The cron daemon has the
#> capability of maintaining 26 different event queues.  Presently
#> only 3 are being used.  Queue 'a' is for 'at(1)' jobs, queue 'b'
#> is for 'batch(1)' jobs, and queue 'c' is for cron jobs.  (For those
#> not running SysV, saying "batch" is almost like saying "at now", but
#> it uses a different queue and at would respond with "at: too late".)
#> So, that means that there are 23 queues presently unused.
#> Unfortunately, there is no way to use these other queues without
#> rewriting a portion of cron, but that's a story for another day.

WRONG WRONG WRONG WRONG WRONG WRONG WRONG WRONG WRONG WRONG

You can specify any of the "other" queues by specifying them on the at(1) 
command line, as in: 

	at -qz now+1hour < jobfile

would cause the commands in jobfile to be executed "out of" the "z" queue an
hour from now.

> As a closing note, cronjobs (as opposed to atobs or batchjobs)
> bypass the queuedefs.  So setting a queue definition for queue 'c'
> will have no effect.

WRONG WRONG WRONG WRONG WRONG WRONG WRONG WRONG WRONG WRONG

Again, you are not correct!  Crontab jobs DO NOT BYPASS THE QUEUEDEFS FILE.  
You can specify definitions for the "c" queue and all crontab jobs will be run 
using them.  

Furthermore, all queues can have a queue definition.  Jobs submitted to a 
particular queue would get those specifications, or if not set in the queuedefs
file, they get the default specifications.  

Sorry, but you should get a source license and read the code.  I have.  


> 				Dave


-- 
			Daniel M. O'Brien (ihnp4!ihlpa!dob)
			AT&T Bell Laboratories  Room IH 4A-257
			Naperville-Wheaton Road,  Naperville, IL 60566