User Profile

Follow-up comment on this Quinn said: "If you use high-level APIs (CFSocketStream, or anything based on that) to create the socket, those APIs do this (set SO_NOSIGPIPE) for you." We're seeing a SIGPIPE when an external process dies, where our process is writing to a fileHandleForWriting from an (NS)Pipe that the external process is reading from. Given the above comment, I would not have expected to receive the signal. Is this the expected behaviour?

Seems like this problem was likely caused by some kind of network filtering on our office network.