BIg picture, I need to ensure a clean startup regardless of how the Apache
instance is stopped. My most recent attempt was to have the startup
program cleanup the associated jobs. Unforunately, my config starts
multiple Apache jobs, so those jobs running the cleanup found new
associated jobs. This resulted in a tangled mess.
The watch idea might work, but I'd need a unqiue MSGID to monitor.
Watching a common message like "job ended" would cause the watch to be
firing way too much.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2021 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
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.