News for hackers. Stuff that matters.
Re:What they don't teach you about sockets by throwaway2037 on Tuesday July 26, 2022 @07:24PM (#32245309)
I have two technical questions after reading this article.

1) The author writes: <<I expected that I would call e.g. isconnected() on the sockets after accept() tells me something happened to it.>> I cannot find any man page for this function. Google also fails me. Is this a hypothetical function or a non-POSIX call?

2) The author writes: <<On Linux, I also needed to disable signaling on the recv() so that I could handle the connection error inline rather than need to register a signal handler. I opted to add the MSG_NOSIGNAL to both send() and recv() and handle potential disconnect errors at each call.>>

I checked the Linux man page for recv(). The flag MSG_NOSIGNAL does not exist (at least in my version). However, send() supports it. Do I misunderstand?

Re:What they don't teach you about sockets by makuto on Tuesday July 26, 2022 @10:06PM (#32246198)
Author here! Isconnected is a hypothetical.