From owner-freebsd-hackers Mon Jan 29 12:48:26 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA01947 for hackers-outgoing; Mon, 29 Jan 1996 12:48:26 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA01933 for ; Mon, 29 Jan 1996 12:48:20 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA04395; Mon, 29 Jan 1996 13:46:30 -0700 From: Terry Lambert Message-Id: <199601292046.NAA04395@phaeton.artisoft.com> Subject: Re: Multi-Port Async Cards To: joerg_wunsch@uriah.heep.sax.de Date: Mon, 29 Jan 1996 13:46:29 -0700 (MST) Cc: freebsd-hackers@FreeBSD.org In-Reply-To: <199601290025.BAA05001@uriah.heep.sax.de> from "J Wunsch" at Jan 29, 96 01:25:02 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org Precedence: bulk > > If the machine crashes, getty goes away (the POST state on a proper serial > > port is to not assert DTR), and so the modems are not answered. > > Hung machines (processes are alive, but context-switch hangs) cause > the modem to pick up the line, but nothing happens. > > Despite of this, i'm still not yet convinced that mgetty is the better > solution. :) A full process table and active mgetty's have the same effect. A bogus shared library and the use of a dynamically linked shell have the same effect. A corrupt shell binary has the same effect. An improper modem setting (improper for mgetty) has the same effect. A lightning hit on a modem has the same effect. If you have a buggered configuration, it is irrelevant how it got that way, only that it IS. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.