From owner-freebsd-current Mon Jun 23 12:14:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA23240 for current-outgoing; Mon, 23 Jun 1997 12:14:50 -0700 (PDT) Received: from veda.is (ubiq.veda.is [193.4.230.60]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA23230 for ; Mon, 23 Jun 1997 12:14:45 -0700 (PDT) Received: (from adam@localhost) by veda.is (8.8.5/8.7.3) id TAA26178; Mon, 23 Jun 1997 19:42:15 GMT From: Adam David Message-Id: <199706231942.TAA26178@veda.is> Subject: Re: getty modem control In-Reply-To: <199706231818.LAA01042@phaeton.artisoft.com> from Terry Lambert at "Jun 23, 97 11:18:33 am" To: terry@lambert.org (Terry Lambert) Date: Mon, 23 Jun 1997 19:42:14 +0000 (GMT) Cc: terry@lambert.org, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > I can cu the device and get a normal response without carrier present. > > However, getty times out trying to send the data, with no flicker on the > > modem TXD. > > I assume this is your modified getty, since regular getty doesn't > send data, right? Mods by David Nugent, which have been in the tree for several months now already. Yes, this is a modified gettytab, since the standard gettytab doesn't cause any command data to be sent. > Look at how 'cu' opens the port. Pay special attention to the > CLOCAL and HUPCL settings. > > Note that you MUST be -CLOCAL, HUPCL for correct dial-in operation > (ie: a modem hangup without logout sends SIGHUP to all processes > in the process group to cause a logout, and logging out drops DTR > to modem to cause it to disconnect). Yes, this is probably where we need to be looking. > Talking to the modem from getty is evil. Something has to initialise it (and reassert initialisation). Also it is useful to interact with the modem on RING, CONNECT and hangup events. -- Adam David