Re: Problem with recv syscall on socket when other side closed

Khimenko Victor (khim@sch57.msk.ru)
Tue, 27 Jun 2000 10:08:10 +0400 (MSD)


In <0006262040080P.00485@dyp> Denis Perchine (dyp@solo.iis.nsk.su) wrote:
>> > > > The if I try to continue read I will get the rest of the data which arrived between last read and
>> > > > connection close... Very strange logic... Any comments on this.
>> > >
>> > > Indeed strange..
>> >
>> > That's why some people do not like linux... Such behavior breaks lots of programs.
>>
>> Assuming it is indeed the kernel that makes the error, and not your
>> program that screws things up.

> The problem occured in postgreSQL 7.0.2. And there is everything fine on FreeBSD & IRIX.
> Only Linux have this problem.

Which problem ? Why you can not stop clients and THEN stop server ? Or there
STILL will be some problems ?

> But I still do not hear the voice of the people who maintain this part of the kernel...

You assuming there are such person :-) It's wrong assumation. AFAIK it was
written by Alan Cox and last who played with is was Andrea Arcangeli so there
are no special maintainer for that code...

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/