>That's what makes them evil to implement in kernel implementation
>of posix_spawn where the path search for posix_spawnp is to be in
>user code (where it belongs).
Why? Our implementation search in the kernel; it is perhaps 20 lines of
code?
> | for the case where PATH, as inherited by the child environment,
>
>The PATH in the child environment seems to be irrelevant (other
>than that is what the child, once it is running, sees).
>
> | has "./" or "../" as initial element of a PATH entry?
>
>You mean any relative path (anything that does not start with a '/').
>There doesn't have to be a '.' to get a PWD relative path (though that
>is certainly one way).
Yeah, that should work though not really recommended :-)
Casper
