Vern Hamberg wrote:
Of course, only when I know that
it'll have no effect on other activity.
Smart. I've been known to move compilation jobs over to the QINTER queue
when the QBATCH queue was clogged and the system was relatively quiet;
while it's certainly possible for two compilation jobs to get in a
fight, it's not especially likely.
And over the weekend, I thought of a simple, but elegant way to keep
programs from fighting with each other, even if their job queue does get
changed to dispatch multiple jobs concurrently.
For the moment, though, since there's only one of me, and I have a
brushfire to put out elsewhere, just having them in a job queue that
keeps them from fighting should do.
--
JHHL
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.