Re: For the almost 4-year anniversary: O_CLOEXEC again

[dean gaudet]

On Sun, 28 Mar 2004, Ulrich Drepper wrote:

> The proposed solution is simple and already implemented on some systems
> (QNX, BeOS, maybe more).  Beside the definition of O_CLOEXEC the
> untested patch below should be all that's needed.  It does *not* solve
> the related problem of socket descriptors etc.  I've no good idea for

we could create new socket, socketpair, accept, and pipe, system calls
with an extra flags argument.  plus some similar solution to account for
dup/dup2/F_DUPFD as well.

how many other fd creating syscalls did i miss? :)

-dean
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/