On Tue, Jun 17, 2008 at 09:48:28AM -0400, David Schultz wrote: > On Tue, Jun 17, 2008, David Xu wrote: > > davidxu 2008-06-17 06:26:29 UTC > > > > FreeBSD src repository > > > > Modified files: > > include Makefile unistd.h > > lib/libc/gen Makefile.inc Symbol.map exec.3 exec.c > > Added files: > > include spawn.h > > lib/libc/gen posix_spawn.c > > Log: > > SVN rev 179838 on 2008-06-17 06:26:29Z by davidxu > > > > Add POSIX routines called posix_spawn() and posix_spawnp(), which > > can be used as replacements for exec/fork in a lot of cases. This > > change also added execvpe() which allows environment variable > > PATH to be used for searching executable file, it is used for > > implementing posix_spawnp(). > > > > PR: standards/122051 > > I have no objections to this, but doesn't it defeat the whole > purpose to implement posix_spawn() as a library function that just > calls fork/exec?
How it can be ? Unless there is some problem with implementation, it shall be ok. Also, SUSv3 explicitely stated that design of the posix_spawn allows it to be implemented as fork/exec.
pgp5bxD7rU8NI.pgp
Description: PGP signature
