In backup2l there is a distiction between STDOUT and STDERR. All errors due to a misbehavior of backup2l or backend tools (i.e. internal problems) go to STDERR, errors such as full backup volumes go to the STDOUT, which contains (and should contain!) a complete log of what went good/bad during the backup. An exception is the --get-available operation, which outputs all log information to STDERR, so that you can easily the availability list to a file.
The '--silent' option can easily implemented by adding "> /dev/null" to /etc/cron.daily/zz-backup2l. However, I do not recommend this at all. Those who do not like e-mail reports (no everybody thinks so) should insert a redirection to a log file of his choice there. Regards, Gundolf On Sat, 2008-08-02 at 03:13 +0100, Noah Slater wrote: > Package: backup2l > Version: 1.4 > Severity: normal > > I'm really sick of getting those damn emails every morning! :) > > I have disabled STDOUT for now, but this is unwise as backup2l does not print > errors to STDERR - so I'm stuck between a rock and a hard place. > > Can you please add a --silent option to this, otherwise very useful, software? > > -- System Information: > Debian Release: lenny/sid > APT prefers unstable > APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, > 'experimental') > Architecture: i386 (i686) > > Kernel: Linux 2.6.20.3-bytemark-uml-2 > Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/bash > > Versions of packages backup2l depends on: > ii findutils 4.4.0-2 utilities for finding > files--find, > > Versions of packages backup2l recommends: > ii tar 1.20-1 GNU version of the tar archiving > u > > Versions of packages backup2l suggests: > ii bzip2 1.0.5-0.1 high-quality block-sorting file > co > pn cdlabelgen <none> (no description available) > > -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
