Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!hao!oddjob!gargoyle!ihnp4!meccts!nis!sialis!rjg
From: rjg@sialis.Sialis.MN.ORG (Robert J. Granvin)
Newsgroups: comp.sys.att
Subject: tty000 'n' uucico
Message-ID: <14@sialis.Sialis.MN.ORG>
Date: Fri, 25-Sep-87 10:32:40 EDT
Article-I.D.: sialis.14
Posted: Fri Sep 25 10:32:40 1987
Date-Received: Sun, 27-Sep-87 10:55:37 EDT
Reply-To: rjg@sialis.mn.org (Robert J. Granvin)
Distribution: world
Organization: Hottentott Horde Rentals, Inc.
Lines: 51

This has probably been discussed before, but I am new here.  :-)

Several folx around here now own AT&T 3b1's, thanks to the fire sale.
Recently, though, some of us discovered what we (at least) consider a
problem.  The description is basically as such:

A remote terminal is attached to tty000.  (These remote terminals
conist of a wide range of machines from Amigas to 'real' terminals to
a Dec III for amusement. :-) 

The problem arises when uucico calls another system.  Normally
everything works fine, but in some situtations, you are forced to send
a BREAK to cycle the answering machines modem to 1200 baud.  The
instant you send the BREAK, tty000 goes out to lunch.  All output to
the device is buffered, and not sent, and input is not accepted from
the terminal.  If you don't send a BREAK, the terminal remains
(apparently) unaffected.

The remote terminal will 'return to life' when the call is complete
and uucico starts up _another_ call.  (The terminal returns at the 
exact same time you hear the relay click to disconnect the remote
phone.  (One exception.  One 3b1 (running v3.5 system and 3.5
utilities) returns the terminal at the end of the call, instead of at
the beginning of the next call).

This has been duplicated on 3b1's running 3.51 system and 3.51
utilities, 3.5 system/3.5 utilities, and 3.5 system/3.51 utilities
(yep.  someone screwed up on the latter one.  :-)

AT&T states they've never heard of this problem, and suggested an
upgrade to 3.51.  The upgrade obviously won't help since it occurs on
3.51 machines as well.

I can't believe that no one else out there has run across this, and I
find it hard to believe that AT&T has no knowledge of it (even though
the person(s) on the phone may not have, though).

Does anyone have any insight/solutions to this?

Email, please.  If there's interest, I'll post a summary.

P.S.  I (unfortunately) missed the discussions regarding the 'can't
open /dev/tty' problem via ph1.  Was there any resolution to this, and
if so, would someone be so kind as to email me a summary?  Thanks.


-- 
 Robert J. Granvin                          UNIVERSE: rjg@Sialis.MN.ORG 
 Programmer/Analyst - Technical Services        UUCP: ihnp4!meccts!sialis!rjg
 National Information Systems, Inc.              ATT: (612) 894-9494
                      "Trust me.  I know what I'm doing"