Package: backupninja
Version: 0.9.3-2
Severity: minor
Tags: patch
I upgraded to backupninja 0.9.3-2 on two hosts this morning and
started getting error messages emailed to me by cron when running
/etc/cron.d/backupninja :
readlink: too few arguments
Try `readlink --help' for more information.
Neither host has any vserver binaries installed. I think
init_vservers() in /usr/lib/backupninja/vserver assumes they are.
The attached patch may not be the cleanest fix, but it supresses the
error message and stops the cron spam.
--Brad
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (990, 'testing'), (500, 'oldstable'), (500, 'unstable'), (500,
'stable'), (1, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-20050918-686-skas3-v8.2
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages backupninja depends on:
ii bash 3.1-1 The GNU Bourne Again SHell
ii dialog 1.0-20060101-1 Displays user-friendly dialog boxe
ii gawk 1:3.1.5-1 GNU awk, a pattern scanning and pr
ii mawk 1.3.3-11 a pattern scanning and text proces
backupninja recommends no packages.
-- no debconf information
--- /usr/lib/backupninja/vserver.orig 2006-02-02 12:30:20.000000000 -0500
+++ /usr/lib/backupninja/vserver 2006-02-02 12:30:27.000000000 -0500
@@ -35,7 +35,7 @@
getconf VSERVER /usr/sbin/vserver
getconf VROOTDIR `if [ -x "$VSERVERINFO" ]; then $VSERVERINFO info SYSINFO
| grep '^ *vserver-Rootdir' | awk '{print $2}'; fi`
# canonicalize VROOTDIR
- VROOTDIR=`readlink --canonicalize $VROOTDIR`
+ VROOTDIR=`readlink --canonicalize $VROOTDIR 2> /dev/null`
# init this library's global variables
vservers_are_available=no
found_vservers=
