From owner-freebsd-questions Thu Jun 17 15:36:40 1999 Delivered-To: freebsd-questions@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 2CC5C15413 for ; Thu, 17 Jun 1999 15:36:14 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id RAA07444; Thu, 17 Jun 1999 17:35:47 -0500 (CDT) (envelope-from dan) Date: Thu, 17 Jun 1999 17:35:46 -0500 From: Dan Nelson To: matt Cc: mike@hyperreal.org, agifford@infowest.com, freebsd-questions@FreeBSD.ORG Subject: Re: ftpd processes stuck in STOR - FreeBSD 3.2 Message-ID: <19990617173546.A7287@dan.emsphone.com> References: <19990617213110.1989.qmail@hyperreal.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: ; from "matt" on Thu Jun 17 18:29:10 GMT 1999 X-OS: FreeBSD 4.0-CURRENT Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Jun 17), matt said: > On Thu, 17 Jun 1999 mike@hyperreal.org wrote: > : Aaron D. Gifford wrote: > : > I'm wondering why my system seems to collect ftpd processes stuck > : > in the STOR state that hang around for days, weeks, > : > : Don't know, but it was something I saw for years on both FreeBSD > : and BSDI, both running old wu-ftpd betas. The solution was to start > : using BeroFTPD. > > I've never had this problem, I run wu-ftpd 2.5.0.. I've also ran the > beta (VR 16+ series) and never had that problem either... odd. It's because stock ftpd doesn't have an idle timeout during data transfer, and if a dialup user disconnects during an up/down load, the ftpd will persist until the system is rebooted. Setting the sysctl net.inet.tcp.always_keepalive=1 works around the problem by disconnecting the socket after two hours. -Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message