tags 826148 -pending +wontfix thanks Addition.
On Mon, Jan 09, 2017 at 06:36:46PM +0100, Mario Lipinski wrote: > >1) monit doesn't support systemd. If you are ready to support this > > package for systemd - please do. > > I just use monit on a Debian system with its default init system. I would > expect monit to work on such a system. If it does not, this should be noted > in the documentation and also probably declare appropriate dependencies > (e.g. to require certain init system or conflict systemd) in the package > meta information. Not sure whether I missed something in this direction. I > already proposed a solution that could work on all systems in my initial > email. Disclamer: systemd-enabled setups are not tested. So, if you feel that there should be direct conflict with systemd - I can add that. But in principle, any LSB-compatible init should work. > >2) "This is not the case when used via monit." - and why it's the monit > > problem, but not systemd*? > > I think that this issue could be handled better on the monit side, but feel > free to forward this to the systemd maintainers. > > I consider the compatibility approach for /etc/init.d (sysvinit) by systemd > very hackish and thus I would prefer a more general solution to control > services. According to > https://www.freedesktop.org/wiki/Software/systemd/Incompatibilities/ calling > init scripts directly is also discouraged by LSB. I don't see service command in LSB: http://refspecs.linuxfoundation.org/LSB_5.0.0/LSB-Common/LSB-Common/rcommands.html Do I miss something? > I was talking about using the /usr/sbin/service binary. In #791667 as far as > I can see only invoke-rc.d was suggested. > > I agree, that maintainer script requirements may not apply to the monit > configuration, but would strongly encourage you to consider a more general > solution for controlling services. > /usr/sbin/service as well as invoke-rc.d (maybe event with --force) seem to > be alternatives worth considering. service can run upstart job, for example, instead of init-file. No, thank you. The point of code snippets in conf-available - be good starting points for your local configuration. If you run upstart job (or run systemd unit, whatever), but monitor init-file instead - something is deeply wrong. If you have idea how to provide better examples, that able to work with different inits - feel free to post a patch. For now, I believe that is't better to use LSB-compatible solution (/etc/init.d/foo start|stop - documented by LSB).
