Package: slbackup Version: 0.0.10-1 Severity: wishlist If we agree that SLBackup should run on the machine were the backup is stored, slbackup will not be able to stop and databases, dump them and then start them again, and will need a separate cronjob on each of the machines it runs on. Would it be better to have slbackup on the backup-machine log into the remote machines and run run-parts /etc/slbackup/pre.d (and later post.d)
It still fails when running ldapdump.sh, but renaming ldapdump.sh to ldapdump solves that bug. -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.13-x300 Locale: LANG=nb_NO, LC_CTYPE=nb_NO (charmap=ISO-8859-1) Versions of packages slbackup depends on: ii debconf 1.4.30.13 Debian configuration management sy pn libconfig-general-p Not found. ii logrotate 3.7-5 Log rotation utility ii perl 5.8.4-8sarge3 Larry Wall's Practical Extraction ii rdiff-backup 1.0.3-1.skolelinux.1 remote incremental backup -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
