Cron has various queues; by convention, a=at, b=batch, c=cron; "c" is actually hard-coded for cron only. But there are actually also queues d through z, which can be used with the -q option of "at".
Limits can be placed on them via queuedefs(4); in particular, for each queue one may set: njobs (maximum number of jobs to run simultaneously in that queue) (default 100), nice (nice number (less favored priority) to run them with) (default 2), and nwait (seconds to wait before rescheduling a job deferred due to njobs limit) (default 60) But what if one wants to disable some of those queues? If I add lines like: d.0j99n99w ... z.0j99n99w that does indeed keep jobs in queues d through z from being run. But it does _not_ prevent them from being submitted. I'd like to see "at" changed to load queuedefs (same code as cron uses, same defaults for queues not explicitly defined in queuedefs), and to immediately reject jobs in any queue where njobs (first number - the maximum number of jobs that may run at once in that queue) is zero. Comments? If additionally, at.allow (or at.deny) could optionally specify a list of queues to which the entry applied, it ought to be possible to restrict cron sufficiently to let more people use it without worrying quite so much about them overloading the system, especially combined with existing project support in "at", and project-based resource controls. -- This message posted from opensolaris.org _______________________________________________ opensolaris-code mailing list opensolaris-code@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
