Salter, James wrote:

If the needed jobqs all are in a particular subsystem, then one option
would be to make sure that the subsystem isn't restarted.

Another thought would be to handle things in the startup program prior
to starting up the system. Do what needs to be done first in the
startup program, then bring the system up.

This seems to me to point to the real question -- Why start subsystems if jobs shouldn't be running in them? If a subsystem hasn't been started, there's no need to hold its jobqs. Only start subsystems that need to do work and the problem doesn't exist.b

Tom Liotta

from: "Steve McKay" <steve.mckay@xxxxxxxxxxx>
subject: Hold ALL jobq's

I'm writing a UPS monitor program and would like to hold all job queues before I shutdown the system so that jobs do not automatically start
running when the system is restarted. Does anyone know of a command or program
that will hold all job queues without my having to create a list of job
queues and read through the list.




As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.