Package: backup-manager
Version: 0.5.8-2
Severity: important
There is a problem with backup-manager which has a great impact on the
robustness of the package: Errors encountered during the creation of
the archives will often go unnoticed. To see what I mean, here is an
example with the relevant variables set as follows:
BM_FILETYPE="tar.gz"
BM_ARCHIVES_REPOSITORY="/tmp/junk"
BM_DIRECTORIES="/etc/ /nonexistent"
Then "backup-manager -v" prints the following (leading and trailing
lines omitted):
...
Creating /tmp/junk/debian-etc.20050717.tar.gz:ok
(1M,6485f90d217a75dc5831332bf6ba25c4)
Creating /tmp/junk/debian-nonexistent.20050717.tar.gz:~ok
(1M,a055d13c14a5f9a5be59d6481eb33226)
...
The _only_ indication of an error (the non-existing source directory)
is that small "~" in the second line, which not many people will
recognize as an error or warning message. The same problem occurs with
other possible tar errors, such as insufficient disk space on the
partition with the archives repository.
I suggest that backup-manager should
- print a warning if tar exits with non-zero status
- return itself a non-zero exit status in that case
- not suppress error messages by tar (if tar prints error messages and
- backup-manager is run via (ana)cron, these messages will be mailed
- to the administrator which seems appropriate to me).
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.31
Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Versions of packages backup-manager depends on:
ii debconf 1.4.30.13 Debian configuration
management sy
ii gzip 1.3.5-10 The GNU compression utility
ii ucf 1.17 Update Configuration File:
preserv
-- debconf information excluded
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
