On Thursday, 24 April 2025 at 19:36:03 UTC, kdevel wrote:
Phobos appears to try and inhibit this on some BSD systems,
How does it do that?
Sorry, I forgot to answer this question. There's a setsockopt
SO_NOSIGPIPE which is used if available during initial socket
setup (in Phobos). Some com
On Thursday, 24 April 2025 at 19:36:03 UTC, kdevel wrote:
[...] I added a SIG_IGN of SIGPIPE and that made the problem
stop.
You know that it will now throw? [0]
Yes; my server was written to handle an exception, and it also is
prepared for the send() to return failure. Adding a third vecto
On Thursday, 24 April 2025 at 14:04:03 UTC, Andy Valencia wrote:
[...]
Phobos appears to try and inhibit this on some BSD systems,
How does it do that?
but on Linux if the recipient has closed the socket and [the
OPs process running his progam] write[s]--SIGPIPE.
"the whole point of the sig
On 25/04/2025 2:04 AM, Andy Valencia wrote:
This has been touched upon way back in forum history, but I thought it
was worth a fresh mention. When writing to a socket--especially as a
server--you can receive SIGPIPE. Phobos appears to try and inhibit this
on some BSD systems, but on Linux if
