Why is writing a closed TCP socket worse than reading one?

by

+1 To Greg Hewgill for leading my thought process in the correct direction to find the answer.

The real reason for SIGPIPE in both sockets and pipes is the filter idiom / pattern which applies to typical I/O in Unix systems.

Starting with pipes. Filter programs like grep typically write to STDOUT and read from STDIN, which may be redirected by the shell to a pipe. For example:

cat someVeryBigFile | grep foo | doSomeThingErrorProne

The shell when it forks and then exec’s these programs probably uses the dup2 system call to redirect STDIN, STDOUT and STDERR to the appropriate pipes.

Since the filter program grep doesn’t know and has no way of knowing that it’s output has been redirected then the only way to tell it to stop writing to a broken pipe if doSomeThingErrorProne crashes is with a signal since return values of writes to STDOUT are rarely if ever checked.

The analog with sockets would be the inetd server taking the place of the shell.

As an example I assume you could turn grep into a network service which operates over TCP sockets. For example with inetd if you want to have a grep server on TCP port 8000 then add this to /etc/services:

grep     8000/tcp   # grep server

Then add this to /etc/inetd.conf:

grep  stream tcp nowait root /usr/bin/grep grep foo

Send SIGHUP to inetd and connect to port 8000 with telnet. This should cause inetd to fork, dup the socket onto STDIN, STDOUT and STDERR and then exec grep with foo as an argument. If you start typing lines into telnet grep will echo those lines which contain foo.

Now replace telnet with a program named ticker that for instance writes a stream of real time stock quotes to STDOUT and gets commands on STDIN. Someone telnets to port 8000 and types “start java” to get quotes for Sun Microsystems. Then they get up and go to lunch. telnet inexplicably crashes. If there was no SIGPIPE to send then ticker would keep sending quotes forever, never knowing that the process on the other end had crashed, and needlessly wasting system resources.

More Related Contents:

  1. What is a magic number, and why is it bad? [closed]
  2. What is the difference between concurrency and parallelism?
  3. Why shouldn’t I use “Hungarian Notation”?
  4. Why should hash functions use a prime number modulus?
  5. What is the difference between currying and partial application?
  6. What is Type-safe?
  7. Solving “Who owns the Zebra” programmatically?
  8. Try to describe polymorphism as easy as you can [closed]
  9. Pass by reference or pass by value? [closed]
  10. How to detect a TCP socket disconnection (with C Berkeley socket)
  11. Making a system call that returns the stdout output as a string
  12. Acronyms in CamelCase [closed]
  13. When is it okay to check if a file exists?
  14. What is the best way to replace or substitute if..else if..else trees in programs?
  15. What is eager loading?
  16. Shortest distance between two line segments
  17. What is the difference between IF-ELSE and SWITCH?
  18. How to deal with constructor over-injection in .NET
  19. How to calculate distance from a point to a line segment, on a sphere?
  20. Followup: Finding an accurate “distance” between colors
  21. What’s the term for the part of the URL after the question mark?
  22. Hash Code and Checksum – what’s the difference?
  23. Is bit shifting O(1) or O(n)?
  24. how to bind raw socket to specific interface
  25. Why is the knapsack problem pseudo-polynomial?
  26. Code Golf: Conway’s Game of Life
  27. What is “backlog” in TCP connections?
  28. Why would a language NOT use Short-circuit evaluation?
  29. Finding closest match in collection of numbers [closed]
  30. Is there a known implementation of an indexed linked list?

Leave a Comment