On 3 Feb 1999, D. J. Bernstein wrote:
> On bug-free systems, the only way for qmail-rspawn to generate that
> message is for execve() to return an error that fails error_temp():
> normally ENOTDIR, ENAMETOOLONG, ENOENT, ELOOP, EACCES, ENOEXEC, E2BIG,
> or EFAULT. None of these can be caused by temporary failures; they are
> permanent (and quite serious) configuration errors.
According to Single Unix Spec v2, execve() may fail with ENOMEM and
ETXTBSY too. And they are interpreted as temporary failures by qmail. You
don't remember the details of your own code. :)
Anyway, I do not think it should be a PERMANENT error when qmail-rspawn
can't execute qmail-remote for WHATEVER reason. Indeed, it is a serious
configuration error if qmail-remote is corrupted, deleted, or having bad
permission but it seems to be a bit harsh not to give an administrator a
chance to fix the problem.
--Pavel Kankovsky aka Peak [ Boycott Microsoft--http://www.vcnet.com/bms ]
"NSA GCHQ KGB CIA nuclear conspiration war weapon spy agent... Hi Echelon!"
