> I would not be opposed to an *option* to ignore all errors. But it
> should not be the default.
Only a little note, to say that after some more test seems that the
''offending'' command that have to be redirected are only two:
gaio@lily:~/conf/spamassassin$ diff -ud spamassassin.squeeze spamassassin
--- spamassassin.squeeze 2012-12-03 18:05:41.516864040 +0100
+++ spamassassin 2012-12-03 18:05:25.540863905 +0100
@@ -29,7 +29,7 @@
# Compile, if rules have previously been compiled, and it's possible
if [ -x /usr/bin/re2c -a -x /usr/bin/sa-compile \
-a -d /var/lib/spamassassin/compiled ]; then
- sa-compile --quiet
+ sa-compile --quiet > /dev/null 2>&1
# Fixup perms -- group and other should be able to
# read and execute, but never write. Works around
# sa-compile's failure to obey umask.
@@ -61,12 +61,12 @@
# Update
umask 022
-sa-update
+sa-update $SA_UPDATE_OPTS
case $? in
0)
# got updates!
- spamassassin --lint || die_with_lint
+ spamassassin --lint > /dev/null 2>&1 || die_with_lint
do_compile
reload
;;
'spamassassin --lint > /dev/null 2>&1 || die_with_lint' i think it is
plausible, because if 'spamassassin --lint', they are recalled without
any redirection, so sysadmin got the info.
'sa-compile --quiet > /dev/null 2>&1' probably have to be digged
better, and handled with more care (also the exit status...).
Not related, see the 'sa-update $SA_UPDATE_OPTS', where
'$SA_UPDATE_OPTS' are defined on /etc/default/spamassassin to load
additional rules (rulesemporium, but does not care).
Thanks.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
