Re: Inadequate documentation: sockets

2001-03-06 Thread Alessandro Baretta
[EMAIL PROTECTED] wrote: > > Hello! > > > The manual specifies the following flag to be returned by the > > kernel > > [smip] > > The information is is not quite correct. > [snip] The information you gave me sounds interesting, but it is conflict with the documentation. This was my original as

Re: Inadequate documentation: sockets

2001-03-06 Thread kuznet
Hello! > The manual specifies the following flag to be returned by the > kernel > > #define POLLHUP 0x0010/* Hung up */ > > Hanging up is ambiguous. Does it mean that the client is dead, > that he closed his end of the socket, or that he shut down one or > both directions of the data flo

Re: Inadequate documentation: sockets

2001-03-06 Thread Khalid Aziz
Alan Cox wrote: > > > =46inally I'm left with my original problem: how am I supposed to > > detect a close or a shutdown from the peer? Once again, I thank in > > advance anyone who will lend me a hand by explaining this to me or > > by addressing me to more adequate documentation. > > By an EOF

Re: Inadequate documentation: sockets

2001-03-06 Thread Alan Cox
> =46inally I'm left with my original problem: how am I supposed to > detect a close or a shutdown from the peer? Once again, I thank in > advance anyone who will lend me a hand by explaining this to me or > by addressing me to more adequate documentation. By an EOF on read or getting SIGPIPE/EPI

Inadequate documentation: sockets

2001-03-06 Thread Alessandro Baretta
Hello everybody! I am a newbie in this list, so please accept my apologies for not being adeqately informed on many technical issues many a kernel programmer might consider banal. I wish to bring your attention to the documentation available on the topic of of the _disconnection_ of stream orien