From owner-freebsd-hackers Thu Dec 14 00:25:55 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA16324 for hackers-outgoing; Thu, 14 Dec 1995 00:25:55 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA16307 for ; Thu, 14 Dec 1995 00:25:49 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id TAA03694; Thu, 14 Dec 1995 19:15:16 +1100 Date: Thu, 14 Dec 1995 19:15:16 +1100 From: Bruce Evans Message-Id: <199512140815.TAA03694@godzilla.zeta.org.au> To: bde@zeta.org.au, yura@rd.zgik.zaporizhzhe.ua Subject: Re: bug or feature in kern/tty.c Cc: eugen@rd.zgik.zaporizhzhe.ua, hackers@FreeBSD.ORG Sender: owner-hackers@FreeBSD.ORG Precedence: bulk >> -l disable modem control (CLOCAL) and ignore carrier detect on >> the slip port. By default the redial-commmand is invoked >> upon carrier drop and slattach aborts if no redial-commmand >> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ >> is specified. >In any case, this not true. Slattach _not aborts_ if no redial-command is >specified. That's because it is broken. It worked in 1.1.5. It was easy to use wirh automatic redial, e.g., `while :; do slattach $slattachargs; done' >... >In 2.1.0 slattach not aborts if modem reconnects, but any output to this line >disabled. You mean this good? Try using a null redial command. This should work unless the DTR drop when the line is closed causes the modem to hang up. This can probably be worked around, e.g., by setting the DTR drop time to a low value (comcontrol /dev/ttyd0 1) or by dsiabling it (stty -hupcl