Three years and six releases later, this is still present :(
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/216847
Title:
sshd will not start at boot if ListenAddress is set, because n
Since I deleted the files by hand, I'm probably not suited to see if it
works now.
--
munin-node after update to Lucid still in /etc/rc*.d, invoked twice
https://bugs.launchpad.net/bugs/574704
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed t
Thanks for the hint.
Indeed, it's still started by upstart and removing /etc/rc?.d and
/etc/init.d/munin-node has no effect on this.
So there should probably be a postinst/postrm for at least /etc/rc?.d.
--
munin-node after update to Lucid still in /etc/rc*.d, invoked twice
https://bugs.launchpa
Public bug reported:
Binary package hint: munin
With system upgrade from Karmic to Lucid, munin-node was upgraded from
1.2.6-13ubuntu3 to 1.4.4-1ubuntu1.
Now on boot, i get the following in /var/log/boot.log:
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility,
same with 1.2.6-13ubuntu1 on a fresh up-to-date karmic.
--
Munin-node have a empty /etc/munin/plugins folder
https://bugs.launchpad.net/bugs/374537
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to munin in ubuntu.
--
Ubuntu-server-bugs ma
