[lwip-devel] [bug #19157] lwip_close problems

[Jonathan Larmour]

Follow-up Comment #16, bug #19157 (project lwip):

Just an information point to confirm what was said earlier, according to
http://www.opengroup.org/onlinepubs/000095399/functions/close.html

"If fildes refers to a socket, close() shall cause the socket to be
destroyed. If the socket is in connection-mode, and the SO_LINGER option is
set for the socket with non-zero linger time, and the socket has
untransmitted data, then close() shall block for up to the current linger
interval until all data is transmitted."

and for the avoidance of doubt,
http://www.opengroup.org/onlinepubs/009695399/functions/setsockopt.html
describes SO_LINGER which says the default is "the system handles the call in
a way that allows the calling thread to continue as quickly as possible".

So the data has to be reliably sent, but if possible, the application should
not block.


    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?19157>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/