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.
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
To post a message email: WEB400@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: WEB400-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.