Re: Checking dirty buffers state of a filehandle (socket) asynchroniously

2004-07-14 Thread Eli Kara
(... after a few minutes) ok, i took my own advice and checked the bible, and it contradicts the info page - shutdown(s, SHUT_WR) will send a FIN _AFTER_ sending any queued data, and will fail any _new_ writes to the socket. Yes that's true (I waited patiently until I got home to check

Re: Checking dirty buffers state of a filehandle (socket) asynchroniously

2004-07-14 Thread Eli Kara
(... after a few minutes) ok, i took my own advice and checked the bible, and it contradicts the info page - shutdown(s, SHUT_WR) will send a FIN _AFTER_ sending any queued data, and will fail any _new_ writes to the socket. Yes that's true (I waited patiently until I got home to check

Re: Checking dirty buffers state of a filehandle (socket) asynchroniously

2004-07-13 Thread guy keren
On Sat, 10 Jul 2004, Shachar Shemesh wrote: The info pages. Do info libc. Scroll down to Function index. Search for shutdown. It has a pretty detailed description of close sending all pending data, and then says: `1' Stop trying to transmit data from this socket. Discard

Re: Checking dirty buffers state of a filehandle (socket) asynchroniously

2004-07-11 Thread shtirlitz
Quoting Shachar Shemesh [EMAIL PROTECTED]: Ori Idan wrote: Shachar Shemesh wrote: Hi all, There are two ways of closing a TCP socket. One is to use close, and the other is to use shutdown. The later allows half-closed sockets (i.e. - one side is closed, the other still open),

Re: Checking dirty buffers state of a filehandle (socket) asynchroniously

2004-07-09 Thread guy keren
On Thu, 8 Jul 2004, Shachar Shemesh wrote: There are two ways of closing a TCP socket. One is to use close, and the other is to use shutdown. The later allows half-closed sockets (i.e. - one side is closed, the other still open), which is a bonus. However, the info page for shutdown states

Re: Checking dirty buffers state of a filehandle (socket) asynchroniously

2004-07-09 Thread Ori Idan
Shachar Shemesh wrote: Hi all, There are two ways of closing a TCP socket. One is to use close, and the other is to use shutdown. The later allows half-closed sockets (i.e. - one side is closed, the other still open), which is a bonus. However, the info page for shutdown states that closing the

Re: Checking dirty buffers state of a filehandle (socket) asynchroniously

2004-07-09 Thread Shachar Shemesh
Ori Idan wrote: Shachar Shemesh wrote: Hi all, There are two ways of closing a TCP socket. One is to use close, and the other is to use shutdown. The later allows half-closed sockets (i.e. - one side is closed, the other still open), which is a bonus. However, the info page for shutdown states

Checking dirty buffers state of a filehandle (socket) asynchroniously

2004-07-08 Thread Shachar Shemesh
Hi all, There are two ways of closing a TCP socket. One is to use close, and the other is to use shutdown. The later allows half-closed sockets (i.e. - one side is closed, the other still open), which is a bonus. However, the info page for shutdown states that closing the write part (i.e. -