My apologies to Dr. Thomas Blinn of Digital Equipment Corp. Our mail
system hiccuped and his original mail message got lost somewhere on
our network, and therefore did not make it into my summary. Here are his
insights on this problem:
I would not be surprised if HP's version of cron accepts something in the
queuedefs file that allows it to dynamically allocate the number of jobs in
each of the queues. Our cron doesn't.
The only thing that will increase the number of simultaneous jobs that our
cron will service is to change the value of MAXRUN. The value that's in
the version of cron that's in development now for the next major release
(which uses a statically allocated table, still) is 25. It's probably not too
late to boost it, and it's not to late to do a patch for the existing version,
either.
Steve, this needs a CLD to get changed for the next major release. It's
not going to get made compatible with HP's implementation, unless
someone comes up with a major justification or HP's code, because it
would be a big project to change what's there now.
==========================================================
Thanks again to everyone who responded to my query. Hopefully, this
problem will be fixed in the not to distant future....
Bob
haskins_at_myapc.com
Received on Tue Nov 21 1995 - 22:36:51 NZDT