Re: RFC: import of posix_spawn GSoC results

[Mouse <mouse%Rodents-Montreal.ORG@localhost>]

> There are a few fancy magic things you can do by passing some of the
> arguments that are NULL in above simplisitic examples, which cause
> the kernel to close or dup file handles, adjust scheduler paramaters
> etc. - in short: everything you would have done in the child process
> after a (v)fork.

This either has a very simplistic idea of what child processes do
between forking and execing/exiting, or it doesn't actually buy you
much.  (What do I suspect it's missing?  flock().  sigaction().
Writing to shared memory.  To name just the first three that come to
mind.)

/~\ The ASCII                             Mouse
\ / Ribbon Campaign
 X  Against HTML                mouse%rodents-montreal.org@localhost
/ \ Email!           7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B