Le dimanche 10 novembre 2013 à 20:23 +0100, Stephan Seitz a écrit : > You don’t want anything like these in your local init service. For such > tests you have Nagios, Icinga or similiar daemons. And they can do much > deeper checks, e.g. can you login into your webservice because your > database backend on a different server is available.
Once your monitoring system – your costly monitoring system with someone behind it just to check whether your buggy scripts have failed to start your service — has detected the service is not running, what will you do to understand what has gone wrong? Please read other people’s arguments before you reply with something completely unrelated. > I don’t mind if you want systemd, but don’t force it on others. There are > no features in systemd that I would dump the well known sysvinit. I don’t mind if you don’t want these features, but don’t force others to run their Debian systems with software from the previous century that lacks them. Nobody is forcing you to use these features. Systemd will keep your precious SysV scripts working just as well as they do right now. The ones who wants to force others to live without the software they need in Debian are the incompetent sysvinit fanboys who lurk around here. kthxbye, -- .''`. Josselin Mouette : :' : `. `' `- -- 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/1384113818.1803.9.camel@tomoe