From owner-freebsd-hackers Wed Dec 13 12:21:53 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA21356 for hackers-outgoing; Wed, 13 Dec 1995 12:21:53 -0800 (PST) Received: from sequent.kiae.su (sequent.kiae.su [144.206.136.6]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA21306 for ; Wed, 13 Dec 1995 12:21:31 -0800 (PST) Received: by sequent.kiae.su id AA28533 (5.65.kiae-2 ); Wed, 13 Dec 1995 23:04:08 +0300 Received: by sequent.KIAE.su (UUMAIL/2.0); Wed, 13 Dec 95 23:04:07 +0300 Received: (from ache@localhost) by ache.dialup.ru (8.7.3/8.7.3) id XAA00533; Wed, 13 Dec 1995 23:03:12 +0300 (MSK) To: Bruce Evans , Terry Lambert Cc: eugen@rd.zgik.zaporizhzhe.ua, hackers@FreeBSD.ORG, yura@rd.zgik.zaporizhzhe.ua References: <199512131818.LAA03398@phaeton.artisoft.com> In-Reply-To: <199512131818.LAA03398@phaeton.artisoft.com>; from Terry Lambert at Wed, 13 Dec 1995 11:18:46 -0700 (MST) Message-Id: Organization: Olahm Ha-Yetzirah Date: Wed, 13 Dec 1995 23:03:12 +0300 (MSK) X-Mailer: Mail/@ [v2.41 FreeBSD] From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) X-Class: Fast Subject: Re: bug or feature in kern/tty.c Lines: 33 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG Precedence: bulk In message <199512131818.LAA03398@phaeton.artisoft.com> Terry Lambert writes: >> >I found strange thing in 2.1.0-RELEASE (and -current) in kern/tty.c. >> >When carrier was lossed then ttymodem() set TS_ZOMBIE and clear >> >TS_CONNECTED in tp->t_state. But TS_ZOMBIE is cleared only in ttioctl() >> >TIOCSETA* when line is setted to ignore modem status and when line is closed. >> >> POSIX says that (what I call the) zombie state remains until the line is >> closed. Clearing it when CLOCAL is raised is a special hack that helped >> very old (1.1.5) versions of slattach and perhaps other broken programs >> work right. >FYI: Of the 120 or so UNIX systems I ported TERM to while I was >at Century Software, only SCO Xenix 2.3.0 behaved this way, and they >fixed it in 2.3.1 after we reported the bug. BTW, it seems we talk about different things. As I understand the original problem, the question is: WHY SLATTACH NOT RECONNECTS WHEN CARRIER ESTABLISHED AGAIN (AUTOMATICALLY BY MODEM)? I.e. 1) driver needs to track carrier when in TS_ZOMBI and set TS_CONNECTED, clear TS_ZOMBI when carrier appearse on the line. 2) Slattach not need exit on SIGHUP but wait reasonable time until carrier will be up again. -- Andrey A. Chernov : And I rest so composedly, /Now, in my bed, ache@astral.msk.su : That any beholder /Might fancy me dead - http://dt.demos.su/~ache : Might start at beholding me, /Thinking me dead. RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849