Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!rutgers!mcnc!ece-csc!ncrcae!ncr-sd!crash!ford
From: ford@crash.CTS.COM (Michael Ditto)
Newsgroups: comp.sys.att
Subject: Re: tty000 'n' uucico
Message-ID: <1812@crash.CTS.COM>
Date: Sun, 4-Oct-87 00:34:48 EDT
Article-I.D.: crash.1812
Posted: Sun Oct  4 00:34:48 1987
Date-Received: Wed, 7-Oct-87 05:34:29 EDT
References: <14@sialis.Sialis.MN.ORG> <4782@ncoast.UUCP>
Reply-To: ford@crash.CTS.COM (Michael Ditto)
Distribution: world
Organization: Crash TS, El Cajon, CA
Lines: 23
Summary: TCSBRK does weird stuff for me too

In article <4782@ncoast.UUCP> allbery@ncoast.UUCP (Brandon Allbery) writes:
>As quoted from <14@sialis.Sialis.MN.ORG> by rjg@sialis.Sialis.MN.ORG (Robert J. Granvin):
 [ ... ]
>| The instant you send the BREAK, tty000 goes out to lunch.
 [ ... ]

I have a similar problem...  I usually log in from a terminal on tty000.
When I am using cu to call out on ph0, everything normally works fine.  But
when I press my BREAK key, OR use the ~%break command to cu, everything
appears to hang (including cu; ^M~..^M does not even get echoed).  Sometimes
hanging up my terminal (dropping DTR for a moment) will get me back to
login:, other times, I have go to the console and kill the cu from there.

It sounds like TCSBRK on ph0 causes tty000 to get hosed, but that doesn't
explain why it hangs when I hit BREAK, unless cu interprets BREAK and does
a ~%break -- maybe it does.


-- 

Michael "Ford" Ditto				-=] Ford [=-
P.O. Box 1721					ford@crash.CTS.COM
Bonita, CA 92002				ford%oz@prep.mit.ai.edu