This bug seems to have come back in jaunty. I have a server munin that
collects data from various client munin machines. This bug (nan for
/var/lock /var/run, etc.) started showing up on my 9.04 box running
munin-node.
/etc/munin/plugins# dpkg -l '*munin*'
Desired=Unknown/Install/Remove/Purge/Hol
This is fixed for jaunty.
** Changed in: munin (Ubuntu)
Status: Confirmed => Fix Released
--
system filesystems are logged within munin
https://bugs.launchpad.net/bugs/175297
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to munin in
FWIW, the bug has been fixed upstream too, see
http://munin.projects.linpro.no/ticket/572
--
system filesystems are logged within munin
https://bugs.launchpad.net/bugs/175297
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to munin in ubuntu.
Revised the patch to also exclude bind-mounted filesystems (which will
always have the same df output as another local filesystem).
** Attachment added: "Revised patch"
http://launchpadlibrarian.net/16495922/munin-df.diff
--
system filesystems are logged within munin
https://bugs.launchpad.ne
This fix was incomplete -- system filesystems are not excluded when the
plugin is reporting its configuration, which results in such filesystems
appearing with usage as 'nan' (not a number).
** Changed in: munin (Ubuntu)
Status: Fix Released => Confirmed
--
system filesystems are logged w
Attaching a patch to fix this.
** Attachment added: "Patch"
http://launchpadlibrarian.net/16495826/munin-df.diff
--
system filesystems are logged within munin
https://bugs.launchpad.net/bugs/175297
You received this bug notification because you are a member of Ubuntu
Server Team, which is sub
