Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

In networking, we need to say EPIPE/SIGPIPE is returned if writing to a closed connection #36

Open
janpgit opened this issue Dec 12, 2017 · 0 comments
Open

In networking, we need to say EPIPE/SIGPIPE is returned if writing to a closed connection #36

janpgit opened this issue Dec 12, 2017 · 0 comments
Labels
content changes to the content

Comments

@janpgit
Copy link
Contributor

janpgit commented Dec 12, 2017

This can be easily demonstrated with tcp/connect and tcp/tcp-sink-server, ie. starting the server, starting the connect client, killing the server, and trying to write data to connect. It exits, $? shows 141.

This needs to be explained somewhere, possibly with the connect() slide.
@vladak vladak added the content changes to the content label Mar 25, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
content changes to the content
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@vladak @janpgit