On Tue, 29 Sep 1998, Peter Radcliffe wrote:
> Child process of procmail_pipe transport returned 67 from command:
>
> While this is useful, its not very informative to those who don't know
> about the existance of sysexits.h.
The problem is that a process started by Exim to run a pipe is entirely
at liberty to return any exit code it fancies. The definitions in
sysexits.h don't seem to have any force of standardization, and indeed,
the comment in the file on Solaris 2.5 says:
* SYSEXITS.H -- Exit status codes employed by the mail subsystem.
*
* This include file attempts to categorize possible error
* exit statuses for mail subsystem.
*
* Error numbers begin at EX__BASE to reduce the possibility of
* clashing with other exit statuses that random programs may
* already return. The meaning of the codes is approximately
* as follows:
> Wish list: translation of the exit code to some more informative text.
> There doesn't seem to be a standard function to do this, but a case
> on EX_foo should be correct.
>
> Since not all programs will return standard exit codes, be able to turn
> it off/on for particular pipe transports ?
Perhaps I can dream up some wording along the line of "a common meaning
of this code is xxxx, but your mileage may vary". For the signals, one
can be more definite. This won't be in the next release because I want
to get that out quite quickly for the bug fix.
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
--
*** Exim information can be found at
http://www.exim.org/ ***
