Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*FD_CLOEXEC\s+doesn\'t\s+take\s+affect\s+through\s+a\s+system\(\"foo\"\)\s+call\?\?\s*$/: 2 ]

Total 2 documents matching your query.

1. elayed_work() (score: 1)

Author: t Xu <herbert@xxxxxxxxxxxxxxxxxxx>

Date: Sun, 30 Jan 2005 22:39:14 -0800

-static and exported) Signed-off-by

/archives/netdev/2005-01/msg01402.html (8,140 bytes)

2. FD_CLOEXEC doesn't take affect through a system("foo") call?? (score: 1)

Author: Ben Greear <greearb@xxxxxxxxxxxxxxx>

Date: Sun, 30 Jan 2005 22:39:14 -0800

I found a funny thing in the 2.6.9 kernel. Not sure if it only happens here, or if it's even a bug, but it was unexpected to me at least... I have a server that opens a listening socket, and sets the

/archives/netdev/2005-01/msg02892.html (7,974 bytes)

Current List: 1 - 2
Page: [1]