[Openmcl-devel] where is OS-level feedback stored when launching an external program that does not exist

Pascal J. Bourguignon pjb at informatimago.com
Tue Apr 17 22:32:20 UTC 2012


"Pascal J. Bourguignon" <pjb at informatimago.com> writes:

> One solution would be for the implementation to create an additionnal
> close-on-exec pipe between the parent and the child, and have the child
> report the errno back to the parent thru the pipe when execve cannot
> work.

Oh, by the way, if this was implemented, it should be only an option.
Unix tries to make it fast to fork new processes, we add three syscalls
to make a close-on-exec pipe to the two syscalls needed to fork and exec
a child, suddenly forking becomes two times slower…

-- 
__Pascal Bourguignon__                     http://www.informatimago.com/
A bad day in () is better than a good day in {}.




More information about the Openmcl-devel mailing list