Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 5/3/83; site umcp-cs.UUCP
Path: utzoo!watmath!clyde!akgua!sdcsvax!sdcrdcf!hplabs!hao!seismo!rlgvax!cvl!umcp-cs!chris
From: chris@umcp-cs.UUCP
Newsgroups: net.unix-wizards
Subject: Re: WOPEN|ISOPEN, etc.
Message-ID: <6935@umcp-cs.UUCP>
Date: Sun, 6-May-84 21:46:32 EDT
Article-I.D.: umcp-cs.6935
Posted: Sun May  6 21:46:32 1984
Date-Received: Wed, 9-May-84 03:28:44 EDT
References: <254@vaxine.UUCP>
Organization: Univ. of Maryland, Computer Science Dept.
Lines: 36

*	From: ptw@vaxine.UUCP

	Is WOPEN set while you sleep for a carrier?

It's supposed to mean ``Waiting for OPEN''.  WOPEN *should*
imply !ISOPEN *for normal usage*, because no one should still be
waiting if someone else has it open.

	Should ISOPEN only be set *after* the carrier comes on?

ISOPEN should be set whenever the line is open.  Typically this
can only be true if the carrier is on (or if it's not on anymore
but some process still has a descriptor to the terminal, which
is actually fairly common... vhangup() was apparently an attempt
to rectify this, but has its own bugs).

	Is there a conventional place to sleep when waiting for
	carrier?  I have seen rawq, outq and tp all used.

Anyplace that's not used by something else... rawq, canq, and
outq aren't likely to be used if no one has the thing open yet.

	Does anybody use BUSY for anything?

Huh?  BUSY?  (I guess not ...)

	How about ASLEEP?

Means the tty is waiting for output to drain, and should be awakend
(on outq I think, too much effort to check from vi here) once the
queue has drained below ttlowat[tp->t_speed].

-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci (301) 454-7690
UUCP:	{seismo,allegra,brl-bmd}!umcp-cs!chris
CSNet:	chris@umcp-cs		ARPA:	chris@maryland