From owner-freebsd-arm@FreeBSD.ORG Wed Jan 30 16:11:53 2013 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id A3EFFB7 for ; Wed, 30 Jan 2013 16:11:53 +0000 (UTC) (envelope-from wynkoop@wynn.com) Received: from mail.wynn.com (wa3yre.wynn.com [199.89.147.3]) by mx1.freebsd.org (Postfix) with ESMTP id 665B7388 for ; Wed, 30 Jan 2013 16:11:52 +0000 (UTC) Received: from ivory.lan (mail.wynn.com [199.89.147.3]) (authenticated bits=0) by mail.wynn.com (8.14.3/8.12.6) with ESMTP id r0UGBpOM088172; Wed, 30 Jan 2013 11:11:51 -0500 (EST) (envelope-from wynkoop@wynn.com) Date: Wed, 30 Jan 2013 11:11:51 -0500 From: Brett Wynkoop To: george@ceetonetechnology.com Subject: Re: arm sshd dies Message-ID: <20130130111151.3fd5e464@ivory.lan> In-Reply-To: <51092781.5020806@ceetonetechnology.com> References: <20130129143240.61bab059@ivory.lan> <1359489256.93359.162.camel@revolution.hippie.lan> <20130129150223.4e095c83@ivory.lan> <20130130053918.7fe366cb@ivory.lan> <51092781.5020806@ceetonetechnology.com> X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.13; x86_64-apple-darwin10.8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jan 2013 16:11:53 -0000 On Wed, 30 Jan 2013 09:00:33 -0500 George Rosamond wrote: > > More details on this would be useful. > > Is it dying with sshd not running, or a dropped connection? The master sshd process dies. Sshd processes that are part of active connections do not seem to die. I have kept ssh connections to the bone for days after applying the first round of patches to the cpsw driver (now part of head). > > sshd_config or ssh_config changes? Anything else, besides patching > cpsw. Nope no other changes. > > (btw, a driver without a man page? ;) > > Does it manually restart? Yep I can jump on the console and /etc/rc.d/sshd start with no problem. > > My BBone hasn't run for more than a few hours at a time, and I've had > no issues with sshd dying, and I've run a bunch of revisions along > the way on CURRENT. > Mine runs 24/7 at this point and is really hungry for usb so it can be building the various ports it wants installed! Please no comments on using nfs. I do not have the ability to do that at the moment. > I'll keep an ssh session connected to the BBones sshd as a test, and > see if I can replicate. No need to keep a session open. Just let your bone stay up and running and then check back at a later time to see if sshd is still running. -Brett -- wynkoop@wynn.com http://prd4.wynn.com/wynkoop/pgp-keys.txt 917-642-6925 718-717-5435 "The strongest reason for the people to retain the right to keep and bear arms is, as a last resort, to protect themselves against tyranny in government" - Thomas Jefferson.