From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28002 invoked by alias); 24 Jan 2003 19:24:56 -0000 Mailing-List: contact overseers-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: , Sender: overseers-owner@sources.redhat.com Received: (qmail 27989 invoked from network); 24 Jan 2003 19:24:55 -0000 Received: from unknown (HELO redhat.com) (66.30.22.225) by 172.16.49.205 with SMTP; 24 Jan 2003 19:24:55 -0000 Received: by redhat.com (Postfix, from userid 201) id 506C41BD7F; Fri, 24 Jan 2003 14:25:00 -0500 (EST) Date: Fri, 24 Jan 2003 19:24:00 -0000 From: Christopher Faylor To: overseers@sources.redhat.com Subject: ssh crash explained Message-ID: <20030124192500.GA12776@redhat.com> Mail-Followup-To: overseers@sources.redhat.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.1i X-SW-Source: 2003-q1/txt/msg00202.txt.bz2 In short: I did it. I scan the system on a regular basis looking for stuck ports using a utility I wrote called "portusage". It appeared that this perl script was running fine on the new system but the output was sufficiently different that I ended up killing what I thought was a stuck ssh process but what was, in fact, the master ssh process. That's not a mistake I will make again, so this should be a non-issue. By "stuck", I mean a process which either has no children and is just sitting around doing nothing or a process which is running something like cvs but has been running for 24 hours. I believe that most of these are due to the people running behind a firewall. I'd hoped that this problem would go away with a newer version of linux and newer version of ssh but I guess it won't just magically disappear. So, I'll be investigating some /proc/sys/net/ipv4 settings this weekend. cgf