many job queue definitions

[Franky Leeuwerck_1]

Hello,

We are in the process of consolidating several sites on 1 machine.

Does anyone has good or bad experience with defining many job (10-20) queue entries in the /var/adm/cron/queuedefs file ?

Franky

[Michael Steele_2]

There are only two lines, a & b.

a is for 'at', limit of 4.

b is for 'batch', limit of 2.

http://docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/B3921-90010/B3921-90010_top.html&con=/hpux/onlinedocs/B3921-90010/00/19/1998-con.html&toc=/hpux/onlinedocs/B3921-90010/00/19/1998-toc.html&searchterms=queuedefs&queryid=20030801-085025

[Ed Sampson]

Yes, we once tried to use it for batch processing and prioritizing of large long running jobs. Some cravats:
1) if you define the queue concurrency as 2 say, and you suddenly release 10 jobs, the 8 non-running jobs will generate requeue messages. The will eventually be picked up by cron on another pass of the queue, but the order will be shuffled around.
2) You need to keep an eye on the maxuprc that
cron has active at any one time. You can overload cron if you have a lot of long running cronjobs.
3) Cron loads the schedule tables in core and
schedules them from there. It's possible that
you could hit a maxdsiz limit for cron, with
a lot of entries.

Other than that it works great.