Why is it assumed that send may return with less than requested data transmitted on a blocking socket?

by

The thing that is missing in above description is, in Unix, system calls might get interrupted with signals. That’s exactly the reason blocking send(2) might return a short count.

More Related Contents:

  1. With C TCP sockets, can ‘send’ return zero?
  2. Are parallel calls to send/recv on the same socket valid?
  3. Setting variable to NULL after free
  4. close vs shutdown socket?
  5. What can be the reasons of connection refused errors?
  6. listen() ignores the backlog argument?
  7. Opaque C structs: various ways to declare them
  8. Get IP address of an interface on Linux
  9. What are the use cases of SO_REUSEADDR?
  10. How to detect a TCP socket disconnection (with C Berkeley socket)
  11. Socket accept – “Too many open files”
  12. Is there a way to flush a POSIX socket?
  13. Using sys/socket.h functions on windows
  14. srand function is returning same values
  15. Receiving multiple multicast feeds on the same port – C, Linux
  16. Why do most C developers use define instead of const? [duplicate]
  17. Why declare a struct that only contains an array in C?
  18. How do I use setsockopt(SO_REUSEADDR)?
  19. Triple pointers in C: is it a matter of style?
  20. Cannot assign requested address – possible causes?
  21. How do I find the current machine’s full hostname in C (hostname and domain information)?
  22. how to bind raw socket to specific interface
  23. How to use SO_KEEPALIVE option properly to detect that the client at the other end is down?
  24. Do you prefer “if (var)” or “if (var != 0)”? [closed]
  25. What can cause a “Resource temporarily unavailable” on sock send() command
  26. Ignoring return values in C
  27. Understanding htonl() and ntohl()
  28. Bind error while recreating socket
  29. passing a struct over TCP (SOCK_STREAM) socket in C
  30. What is the difference between AF_INET and PF_INET in socket programming?

Leave a Comment