File descriptor handling changes in 2.6.27
Posted Aug 4, 2008 19:30 UTC (Mon) by
jreiser (subscriber, #11027)
In reply to:
File descriptor handling changes in 2.6.27 by spotter
Parent article:
File descriptor handling changes in 2.6.27
Why can't one close the fd's in the child before exec()?
The problem is knowing/deciding/communicating which fd should be closed, and getting everybody to do the correct close().
Once fork() occurs, shouldn't no more fd's be added to the child?
Redirecting stdin/stdout/stderr to an explicit path adds a new fd to the child.
(
Log in to post comments)