** Changed in: munin (Debian)
Status: Unknown = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to munin in Ubuntu.
https://bugs.launchpad.net/bugs/406276
Title:
initial munin-node setup misses correct start/stop
** Branch linked: lp:ubuntu/karmic/munin
--
initial munin-node setup misses correct start/stop
https://bugs.launchpad.net/bugs/406276
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to munin in ubuntu.
--
Ubuntu-server-bugs mailing list
** Changed in: munin (Ubuntu)
Status: Triaged = In Progress
** Changed in: munin (Ubuntu)
Assignee: (unassigned) = Thierry Carrez (ttx)
--
initial munin-node setup misses correct start/stop
https://bugs.launchpad.net/bugs/406276
You received this bug notification because you are a
This bug was fixed in the package munin - 1.2.6-13ubuntu2
---
munin (1.2.6-13ubuntu2) karmic; urgency=low
* Don't autoconf the plugin postgres_space_ (LP: #414232)
* Restart munin-node after plugin initiation (LP: #406276)
-- Andreas Olsson an...@ubuntu.com Thu, 20 Aug 2009
I can confirm this bug in Jaunty (munin-node 1.2.6-8ubuntu3) as well as
in Karmic (munin-node 1.2.6-8ubuntu3).
** Changed in: munin (Ubuntu)
Importance: Undecided = Low
** Changed in: munin (Ubuntu)
Status: New = Confirmed
--
initial munin-node setup misses correct start/stop
Actually, there is a munin-node 1.2.6-12ubuntu1 uploaded to Karmic. It
just haven't reached the archives yet, due to an i386 build issue. I
did a local build of munin-node 1.2.6-12ubuntu1, and it still contains
this bug.
Anyway, this problem can be fixed by editing debian/munin-node.postinst
and
