>From my point of view managing sub-processes / service with Monit is good.
For the "crap" part I was more speaking about the job of the Monit package maintainer. for this kind of reason, I use packages/binaires from the Monit website instead of the OS repositories or third party like EPEL. 2017-10-24 17:48 GMT+02:00 Guillaume François < [email protected]>: > When told to shutdown the OS should stop all services, including Monit, > shouldn't it? > > -> It depends of how it was package for CentOS. And operating system > supervisor will only handle processes it managed and know how to manage. > > If CentOS package maintainer did crap integration for Monit in CentOS, it > won't stop itself. Best is to perform a test on a clean system only with > Monit and see the behavior. > > On your CentOS version, how is Monit managed (start/stop) by the operating > system ? Do it use system.d script ? service scripts ? init script ? > > In the past, when requiring OS shutdown, after some time (timeout reach), > the operating systems were issuing a soft kill then a hard kill signal. > This is not the case anymore as all processes *should *be managed by > operation system supervisor like upstart or system.d > > Note that should is not a MUST. It people do crap, they have to clean up > their crap. > > > > 2017-10-24 17:26 GMT+02:00 Nick Upson <[email protected]>: > >> the processes that monit controls are fully controlled by monit, so the >> OS doesn't touch them >> >> When told to shutdown the OS should stop all services, including monit, >> shouldn't it? >> >> On 24 October 2017 at 16:21, Guillaume François < >> [email protected]> wrote: >> >>> Hello, >>> >>> Are you using Monit to restart the processes when they "fail" ? If >>> shutdown process stop them but Monit start them back you'll go into a loop >>> mostly. Il already encountered this kind of loop. >>> >>> Anyway, it would be better to stop Monit as part of the shudown process >>> no ? >>> >>> Best Regards. >>> >>> 2017-10-24 17:16 GMT+02:00 Nick Upson <[email protected]>: >>> >>>> Hi >>>> >>>> I have several virtual centos 6.8 x64 VM's with monit-5.14-1.el6.x86_64 >>>> installed. I am finding that I can tell a VM to shutdown (either from the >>>> hypervisor or commandline), the standard message is sent and then it >>>> doesn't shutdown. I've waited hours and no shutdown, If I stop monit >>>> however at that point the shutdown proceeds normally. >>>> >>>> Has anyone seen this? would a more up-to-date version fix it? >>>> >>>> (Oh and its not consistent, sometimes the system does shutdown) >>>> >>>> >>>> -- >>>> To unsubscribe: >>>> https://lists.nongnu.org/mailman/listinfo/monit-general >>>> >>> >>> >>> >>> -- >>> -----BEGIN GEEK CODE BLOCK----- >>> Version: 3.1 >>> GCS/IT d(+) s++:- a C++$ ULC(+)>+++$ !P--- L+>$ !E---? W+++$ !N* !o-- >>> K--? w(+) !O---? !M- !V--? PS+? !PE Y+ PGP++>+++ !t-- !5 !X- R(+)>++* tv-? >>> b(-) DI !D- G(+)>+ e+++ h--() r->$ y?* >>> ------END GEEK CODE BLOCK------ >>> >>> -- >>> To unsubscribe: >>> https://lists.nongnu.org/mailman/listinfo/monit-general >>> >> >> >> -- >> To unsubscribe: >> https://lists.nongnu.org/mailman/listinfo/monit-general >> > > > > -- > -----BEGIN GEEK CODE BLOCK----- > Version: 3.1 > GCS/IT d(+) s++:- a C++$ ULC(+)>+++$ !P--- L+>$ !E---? W+++$ !N* !o-- K--? > w(+) !O---? !M- !V--? PS+? !PE Y+ PGP++>+++ !t-- !5 !X- R(+)>++* tv-? b(-) > DI !D- G(+)>+ e+++ h--() r->$ y?* > ------END GEEK CODE BLOCK------ > -- -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCS/IT d(+) s++:- a C++$ ULC(+)>+++$ !P--- L+>$ !E---? W+++$ !N* !o-- K--? w(+) !O---? !M- !V--? PS+? !PE Y+ PGP++>+++ !t-- !5 !X- R(+)>++* tv-? b(-) DI !D- G(+)>+ e+++ h--() r->$ y?* ------END GEEK CODE BLOCK------
-- To unsubscribe: https://lists.nongnu.org/mailman/listinfo/monit-general
