> monit is not about its web gui. It is a system for proactive > monitoring, and these features of monit can conflict with > systemd's configuration (e.g. Restart=on-failure). Yes, I know that monit is really useful with stateless init systems. But it can also be useful with others. I don't know how the dependency solver handles this, but right now, monit will trigger sysvinit installation, but systemd-sysv will remove it, as it is referenced as a conflict. If systemd is a real problem for monit, it should be better to add systemd (or systemd-sysv) as a conflictual package.
I am not trying to push systemd nor sysv. I am just trying to avoid a war for future users :) And I think monit still has some features that could be useful, even when services are not run by sysv, such as checking processes by sending them some TCP bytes and analyze the answer. Adrien -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
