Because in Unix most services are enabled or disabled via classic commands /etc/init.d/foo start, or handling links in rc3.d. messing cron files is counter intuitive.
Systems replaces init.d and rc3.d with systemctl. Good. Init.d/munin never existed, and was never needed in the past, why did you even care creating a link from munin to /dev/null ? We run systemctl as habit like for ssh and apache. Creating a systemd file for munin is a good idea. Using systemctl to enable and start munin would be nice. Or : make the .service file show a messages to tell to edit cron files. Le 11 mars 2017 19:46:29 CET, Andreas Henriksson <[email protected]> a écrit : >On Sat, Mar 11, 2017 at 11:04:25AM +0000, Holger Levsen wrote: >[...] >> however, all that /etc/init.d/munin really does, is "mkdir && chown >/var/run/munin". >> >> that's all we need as a service file to fix this bug. Pretty trivial. >Still, >> help welcome. >[...] > >No, there's no need for a service file since it's already implemented >in a much better way: > >https://sources.debian.net/src/munin/2.0.33-1/debian/munin-common.tmpfile/ > >What needs to happen is that people explain why they so desperately >is trying to run the init script! Or what's unclear about the "masked" >message they get when trying to start munin.service. > >(Likely this bug report should be closed as "not a bug". People here >just seem to be very confused. Nothing to see please move along?!) > >Regards, >Andreas Henriksson -- Benoît-Pierre Demaine. Typos sponsorisées par mon téléphone.
