I know I may have asked this question before, and the think the common answer was "reboot".  Just curious if when the job limit counter and the jobs executing gets "out of sync" (i.e. job limit is 18 and only 16 will execute) if there is a way to fix it without the dreaded reboot.  We do not have multiple job queues setup, and are on 7.0.  I know we have talked to the folks at Beechglen too, and I believe all you can do is reboot.  Just wondering if anyone else on the list has figured out a way to go into debug or whatever and fix the issue without a reboot, assuming whatever is done does not cause the box to go brain dead or go unstable and need a reboot anyway.  I know rebooting should not be considered that big of a deal, but in our situation, a "planned" reboot needs lots of prior notification to the user base (2 weeks is the "preferred" number), and has never been taken very positively by the user base, if you know what I mean.

Mike Baker


DISCLAIMER:
**This communication, along with any documents, files or attachments, is intended only for the use of the addressee and may contain legally privileged and confidential information. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of any information contained in or attached to this communication is strictly prohibited. If you have received this message in error, please notify the sender immediately and destroy the original communication and its attachments without reading, printing or saving in any manner. This communication does not form any contractual obligation on behalf of the sender, the sender's employer, or the employer's parent company, affiliates or subsidiaries.**

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *