]] Sergey B Kirpichev > >> Usually, you want to start this service last and stop first. > > > > Why should it start last? > > Because monit is not systemd. monit - is only an utility for > proactive monitoring, not yet another init-replacement. > > So, lets start services first, then start monitoring. Do > we want to play races with sysvinit? No. Now can you see the point?
An init system that doesn't handle the case of something going «please start $service» when it's already in the process of starting that service, is buggy. > > but it should probably then just integrate with the init > > system so it knows if the system is about to shut down and > > then avoid restarting daemons. > > The above use case is just a simplest example of such > integration. It's sysvinit responsibility to start/stop monit > as appropriate. Sure, worst case is that monit, in the middle of shutting down, requests a service start which won't ever happen (because the machine will be shut down by then). -- Tollef Fog Heen UNIX is user friendly, it's just picky about who its friends are -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/871tzgqev4....@xoog.err.no
