From owner-freebsd-questions Tue Oct 21 13:57:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA09311 for questions-outgoing; Tue, 21 Oct 1997 13:57:37 -0700 (PDT) (envelope-from owner-freebsd-questions) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA09299 for ; Tue, 21 Oct 1997 13:56:56 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id NAA12120; Tue, 21 Oct 1997 13:59:01 -0700 (PDT) Message-Id: <199710212059.NAA12120@implode.root.com> To: Dev Chanchani cc: Doug White , freebsd-questions@FreeBSD.ORG Subject: Re: ftpd hanging around In-reply-to: Your message of "Tue, 21 Oct 1997 13:23:49 EDT." From: David Greenman Reply-To: dg@root.com Date: Tue, 21 Oct 1997 13:59:01 -0700 Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Most of the FTP's seem to be in sbwait. >They hang around indefinatly, or so it seems, they just seem to >accumulate. > >I don't know what client the remote end is using, its a fairly public >server. > >Doesn't ftp timeout though? I mean, can someone just leave an ftp server >running? I thought it timed out and closed after 900 seconds? Sort of. If they are idle in the command loop, then they will time out. If they are stuck waiting to receive a file (perhaps from a machine that is no longer even powered on), they will not. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project