POSIX close(2) is broken

Re:POSIX close(2) is broken by nknight on Saturday December 17, 2011 @04:18AM (#3363875)

Yeah, I was just looking at that after I posted my initial comment, and I think I agree with you. That's the only reading I can see that doesn't create more questions than it answers.

I think in this case, Occam's razor says "this part of the standard is not fully thought through".

[ Parent | on HN ]

Re:POSIX close(2) is broken by cperciva on Saturday December 17, 2011 @04:42AM (#3363910)

this part of the standard is not fully thought through

I agree... and this terrifies me, given that EINTR is mentioned in the man page for close(2) back in BSD Net/2, over 20 years ago.

[ Parent | on HN ]

Re:POSIX close(2) is broken by ajasmin on Saturday December 17, 2011 @08:36AM (#3364202)

this terrifies me

Now think about all the libraries and application that end up calling close() and fclose().

Add a few abstraction layers and good luck figuring out if closing a file is safe in a multithreaded Java app.

[ Parent | on HN ]