From owner-freebsd-current@FreeBSD.ORG Sat Sep 18 15:52:05 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B8A1916A4CE for ; Sat, 18 Sep 2004 15:52:05 +0000 (GMT) Received: from web50709.mail.yahoo.com (web50709.mail.yahoo.com [206.190.38.250]) by mx1.FreeBSD.org (Postfix) with SMTP id 6DA7C43D31 for ; Sat, 18 Sep 2004 15:52:05 +0000 (GMT) (envelope-from w8hdkim@yahoo.com) Message-ID: <20040918155204.71955.qmail@web50709.mail.yahoo.com> Received: from [68.40.135.37] by web50709.mail.yahoo.com via HTTP; Sat, 18 Sep 2004 08:52:04 PDT Date: Sat, 18 Sep 2004 08:52:04 -0700 (PDT) From: Kim Culhan To: freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Serial port activity can make 5.3-BETA4 inaccessable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Sep 2004 15:52:05 -0000 I made the mistake of cross-connecting two serial ports to allow access to the consoles of either machine from the other. Both machines were rebooted at the same time. At the moment I'm hoping the guy with the key to the colo space wakes up soon so I can go there and save things.. Is there a way to prevent the 'login: deadlock' from rendering both machines inaccessable from the network ? -kim _______________________________ Do you Yahoo!? Declare Yourself - Register online to vote today! http://vote.yahoo.com