Hi Tom,
thanks for you very quick and helpful answers (<- plural).
> This is a known issue in munin 1.4.0 upgrading from 1.2.6. It is
> documented in the upstream release notes, and also packaged in the munin
> package at: /usr/share/doc/munin/UPGRADING
I really suggest that a link to this is inserted in NEWS.Debian.gz,
because that file displayed on many machines by apt-listchanges.
> Here's the relevant text from the /usr/share/doc/munin/UPGRADING file:
[snip]
> There is no really reliable way to fix this or migrate automatically.
I see that there is no reliable way to migrate. This is especially true
because devices like tmpfs are often mounted to various places. However
in many cases the rename is unique. A script to fix common (lvm)
filename migrations should not be that difficult.
$ cat munin-fix-df.sh
#!/bin/sh
set -e
for plugin in df df_inode; do
for file in *-$plugin-*-g.rrd; do
test -e "$file" || continue
hostpart="${file%%-$plugin-*}"
lastpart="${file##$hostpart-$plugin-}"
target="${lastpart%-g.rrd}"
# only names with length > 19 are a problem
test ${#target} -gt 19 || continue
# take the last 19 bytes, the twentieth is newline
shorttarget=`echo $target | tail -c20`
oldfile="$hostpart-$plugin-$shorttarget-g.rrd"
test -e "$oldfile" || continue
echo "suggest renaming: $oldfile $file"
done
done
$
Hope it helps
Helmut
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
