On Sun, Feb 11, 2001 at 09:05:07PM +, Chris Evans wrote:
>
> On Sun, 11 Feb 2001, Andi Kleen wrote:
>
> > On Sun, Feb 11, 2001 at 08:41:04PM +, Chris Evans wrote:
> > >
> > > [cc: Andi]
> >
> > Missing context..
>
> [...]
>
> > What do you exactly think is wrong?
>
> man socket(7) say
On Sun, 11 Feb 2001, Andi Kleen wrote:
> On Sun, Feb 11, 2001 at 08:41:04PM +, Chris Evans wrote:
> >
> > [cc: Andi]
>
> Missing context..
[...]
> What do you exactly think is wrong?
man socket(7) says that setting SO_LINGER on a socket will make shutdown()
and close() block. That's incor
On Sun, Feb 11, 2001 at 08:41:04PM +, Chris Evans wrote:
>
> [cc: Andi]
Missing context..
>
> On Sun, 11 Feb 2001 [EMAIL PROTECTED] wrote:
>
> > Hello!
> >
> > > I'm not seeing shutdown(2) block on a TCP socket. This is Linux kernel
> > > 2.2.16 (RH7.0). Is this a kernel bug, a documentat
[cc: Andi]
On Sun, 11 Feb 2001 [EMAIL PROTECTED] wrote:
> Hello!
>
> > I'm not seeing shutdown(2) block on a TCP socket. This is Linux kernel
> > 2.2.16 (RH7.0). Is this a kernel bug, a documentation bug,
>
> Man page is wrong.
Yes, man socket(7) seems to be wrong.
I don't have access to a ge
Hello!
> I'm not seeing shutdown(2) block on a TCP socket. This is Linux kernel
> 2.2.16 (RH7.0). Is this a kernel bug, a documentation bug,
Man page is wrong.
What's about kernel... Hmm, actually, it is worth to test genuine bsd.
Such feature could be useful.
Alexey
-
To unsubscribe from this
Hi,
>From socket(7):
SO_LINGER
...
When enabled, a close(2) or shutdown(2) will not
return until all queued messages for the socket
have been successfully sent or the linger timeout
has been reached.
I'm not seeing shutdow
6 matches
Mail list logo
