Our automation simply issues S IHSDOWN when we want to shut down IHS. That STC has the apachectl -k stop coded. We start it with S IHS1.
On Wed, Dec 6, 2017 at 9:25 AM Jantje. <jan.moeyers...@gfi.be> wrote: > On Wed, 6 Dec 2017 14:51:45 +0000, Nims,Alva John (Al) <ajn...@ufl.edu> > wrote: > > >I too am in the middle of switching servers and I believe IBM says you > have to use the "apachectl -k stop", because more than one instance of the > WebServer is started, so the "apachectl -k stop" shuts all of them down. > > Well... That is indeed one possibility and from my testing it seems to > work most (but not all) of the time. The issue I have with that approach is > that it is not automation-friendly IMHO. A modify or stop command just > ought to work. > > IBM has written the apache module for it, shouldn't they just make it work? > > And yes, I know, there will be multiple processes, but they are all under > control of the master httpd daemon process. It should be able to find all > it's children. I does when spoken to via apachectl, why would it not when > spoken to via some other means of communication? > > Thanks and very best regards, > > Jantje. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
