Your message dated Wed, 21 Jun 2006 16:17:36 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#374825: don't exit with non-zero exit code in absence of
errors
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: clamav-freshclam
Severity: normal
Version: 0.88.2-0volatile1
embryo:~# freshclam
ClamAV update process started at Wed Jun 21 14:48:53 2006
main.cvd is up to date (version: 39, sigs: 58116, f-level: 8, builder: tkojm)
daily.cvd is up to date (version: 1558, sigs: 1957, f-level: 8, builder:
ccordes)
embryo:~# echo $?
1
--
Please do not send copies of list mail to me; I read the list!
.''`. martin f. krafft <[EMAIL PROTECTED]>
: :' : proud Debian developer and author: http://debiansystem.info
`. `'`
`- Debian - when you have better things to do than fixing a system
signature.asc
Description: Digital signature (GPG/PGP)
--- End Message ---
--- Begin Message ---
also sprach Stephen Gran <[EMAIL PROTECTED]> [2006.06.21.1556 +0200]:
> freshclam
>
> you have to write:
> if freshclam; then ... fi
>
> which you should be doing in a set -e script anyway.
Why? If I want the script to end when freshclam fails, I now have to
do:
if ! freshclam; then
ret=$?
[ $ret -gt 1 ] && exit $ret
# no error
fi
That's just highly annoying for no added benefit.
> If by finishes, you mean exits, there are a number of things freshclam
> can exit from, but that doesn't mean it exited successfully. Unless you
> want to parse output, return codes provide a good way to communicate
> back status. This is fairly traditional behavior.
It's traditional behaviour for a non-zero exit code to indicate
failure, yes, and for multiple return codes to distinguish among
different failures.
> I agree it's not necessarily expected, but I tend to disagree that
> it's a problem.
Fine. I'll close this bug then. I can't be bothered to argue for
such a minor point.
--
Please do not send copies of list mail to me; I read the list!
.''`. martin f. krafft <[EMAIL PROTECTED]>
: :' : proud Debian developer and author: http://debiansystem.info
`. `'`
`- Debian - when you have better things to do than fixing a system
signature.asc
Description: Digital signature (GPG/PGP)
--- End Message ---
