Package: munin-node
Version: 1.2.5-1
Severity: normal

When aptitude-installing munin and munin-node, the following was
reported during setup of munin-node:

Setting up munin-node (1.2.5-1) ...
Initializing plugins..ln: creating symbolic link 
`/etc/munin/plugins/ip_0.0.0.0/0' to `/usr/share/munin/plugins/ip_': No such 
file or directory
ln: creating symbolic link `/etc/munin/plugins/ip_xxx.xxx.xxx.xxx/xx' to 
`/usr/share/munin/plugins/ip_': No such file or directory
ln: creating symbolic link `/etc/munin/plugins/ip_xxx.xxx.xxx.xxx/xx' to 
`/usr/share/munin/plugins/ip_': No such file or directory
[...]
ln: creating symbolic link `/etc/munin/plugins/ip_xxx.xxx.xxx.xxx/xx' to 
`/usr/share/munin/plugins/ip_': No such file or directory
done.

(Actual IPs from my iptables config removed, and list shortened).

These seem to come from the suggest method of the ip_ wildcard pluging.

The problem is that the return values of that method can contain slashes,
which are not escaped before being passed to ln.  ln, in turn, complains
because there is noe directory called /etc/munin/plugins/ip_0.0.0.0/
where it can create the symlink 0.

-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-2-k7
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages munin-node depends on:
ii  adduser                       3.102      Add and remove users and groups
ii  libnet-server-perl            0.94-1     An extensible, general perl server
ii  lsb-base                      3.1-22     Linux Standard Base 3.1 init scrip
ii  perl                          5.8.8-7    Larry Wall's Practical Extraction 
ii  procps                        1:3.2.7-3  /proc file system utilities

Versions of packages munin-node recommends:
ii  libnet-snmp-perl              5.2.0-1    Script SNMP connections

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to