From owner-freebsd-stable Mon Oct 9 10:10:59 2000 Delivered-To: freebsd-stable@freebsd.org Received: from yertle.kciLink.com (yertle.kciLink.com [205.252.34.9]) by hub.freebsd.org (Postfix) with ESMTP id D771C37B503 for ; Mon, 9 Oct 2000 10:10:53 -0700 (PDT) Received: by yertle.kciLink.com (Postfix, from userid 100) id 1F4C32E443; Mon, 9 Oct 2000 13:10:52 -0400 (EDT) From: Vivek Khera MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14817.64539.984808.362682@yertle.kciLink.com> Date: Mon, 9 Oct 2000 13:10:51 -0400 (EDT) To: stable@freebsd.org Subject: effective use of serial console X-Mailer: VM 6.72 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've got a stack of servers at a co-lo facililty about 35 minutes drive from here (non-rush hour...) and I'd like to make best use of the serial console feature of FreeBSD. So far with my in-office experiments, I have been able to do just about everything I need. My only question is how can I force a reboot similar to the CTL-ALT-DEL key sequence on a local console? I was hoping a BREAK signal would do it, but the best I can do is make it drop to a debugger. I don't really need debugger support in my production kernels, but I guess if that's the only way to accomplish it... How do others set this up? I guess I'm really looking for a really fail-safe serial console. Thanks. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-301-545-6996 GPG & MIME spoken here http://www.khera.org/~vivek/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message