From owner-freebsd-questions Sun Mar 11 22:51:24 2001 Delivered-To: freebsd-questions@freebsd.org Received: from bryden.apana.org.au (bryden.apana.org.au [203.3.126.129]) by hub.freebsd.org (Postfix) with ESMTP id 9BF9637B718 for ; Sun, 11 Mar 2001 22:51:19 -0800 (PST) (envelope-from dougy@bryden.apana.org.au) Received: from roadrunner (roadrunner.apana.org.au [203.3.126.132]) by bryden.apana.org.au (8.11.1/8.11.1) with SMTP id f2C6p4q00731; Mon, 12 Mar 2001 16:51:05 +1000 (EST) (envelope-from dougy@bryden.apana.org.au) Message-ID: <010001c0aac0$f4116f80$847e03cb@apana.org.au> From: "Doug Young" To: "Kris Kennaway" Cc: References: <009701c0aabd$9758e460$847e03cb@apana.org.au> <20010311223418.A28355@mollari.cthul.hu> Subject: Re: SSH issue Date: Mon, 12 Mar 2001 16:52:02 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 12, 2001 at 04:28:00PM +1000, Doug Young wrote: > What would cause SSH to apparently die after a reboot of a remote 4.2 box ?? > Its been working fine up to now & I'm not aware of any significant events > that would have given the box a fright. Did you recently upgrade that box, and forget to run mergemaster? No ... it was left doing a buildworld but the first time we noticed that ssh had died was after getting back home (the box is colocated at our upstream provider in the city). I wouldn't have thought that the buildworld would cause trouble though .... its not as if its got to installing yet (I'll go do that stuff in person) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message