I'm also affected by this issue I think. I don't know for now whether it has something to do with systemd or startup, but if the munin-node service gets started with "start munin-node", it can't be stopped with "/etc/init.d/munin-node stop" although it went "[OK]". Also "/etc/init.d /munin-node restart" won't work anymore, it the service has been brought up via "start munin-node".
The same effect occurs vice versa: if you start the node with "/etc/init.d/munin-node start", you can't control it by upstart controls. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1270193 Title: /etc/init.d/munin-node not systemd compliant To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/munin/+bug/1270193/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
