×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I admit that it can be nice not to have to wait for another user to
notice his or her locked-up compilation job, but what if you've got two
batch-by-design jobs that could get into a fight with each other if
allowed to run concurrently?
For probably the fourth or fifth time, I had to clean up a mess that was
partly caused by two batch jobs (running the same program!) getting into
exactly that sort of fight, for exactly that reason.
Isn't "running jobs sequentially, one at a time" the essence of batch
processing?
Why it took me until now to fix it so that they'd be explicitly run
through a "normal" batch queue instead of the default "abby-normal" one,
I dunno.
--
JHHL
This mailing list archive is Copyright 1997-2024 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.
midrange.com
