|
From: Oswald B. <os...@kd...> - 2005-10-05 07:50:02
|
On Wed, Oct 05, 2005 at 12:07:34AM +0100, sv...@va... wrote:
> If the launcher can't figure out what it's own name is, don't bail
> out. Instead, print a warning message, continue, and cause any
> attempt to trace into a child process to fail with ECHILD.
>
that's no valid error code for execve() - not that any app i know would
care. apart from that the situation doesn't really match the intended
interpretation of this error code. ENOENT is very generic and certainly
confusing when shown to the user ("huh? <program> *is* there ..."),
but the explanation in the linux execve() man page fits pretty well.
</pedant>
--
Hi! I'm a .signature virus! Copy me into your ~/.signature, please!
--
Chaos, panic, and disorder - my work here is done.
|