Subject: Re: ftpd never dies (again)
To: NetBSD current users <current-users@netbsd.org>
From: Eric Delcamp <e.delcamp@wanadoo.fr>
List: current-users
Date: 03/27/1999 23:55:54
Hi !

Hum, if netstat list the connections as ESTABLISHED, and if it's due to
users that break connections during a command that send data (like STOR), I
think ftpd is not guilty to wait forever.
I'm really not sure, but if a socket is broken, the client receive a message
saying "hey, it's broken". If ftpd never receive this kind of message, it
has no reason to stop waiting.

Really, I'm not sure, just a guess....
---
Eric Delcamp...........................NetBSD i386 & Amiga, BeOS, Windows NT
Merignac...............................Distributed.net : < 6300th (25/03/99)
France.................................Magic the Gathering player
http://perso.wanadoo.fr/eric.delcamp/ .ICQ:34110772

-----Message d'origine-----
De : Allen Briggs <briggs@canolog.ninthwonder.com>
À : Eric Delcamp <e.delcamp@wanadoo.fr>; NetBSD current users
<current-users@netbsd.org>
Date : samedi 27 mars 1999 23:26
Objet : Re: ftpd never dies (again)


>> I don't think these dialup users stay logged on for 3-4 weeks without
>> disconnecting... ;)  (The oldest ftpd processes had been hanging around
>> since February..)  And they were all in that STOR state, according to ps.
>I'm seeing this too, it seems to happen when remote users get cut off
>due to network lossage of one sort or another.  I see it in STOR or RETR
>or sometimes LIST.  netstat lists the connections as ESTABLISHED.