Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/5/84; site mnetor.UUCP
Path: utzoo!utcs!mnetor!clewis
From: clewis@mnetor.UUCP (Chris Lewis)
Newsgroups: net.dcom,net.bugs.uucp
Subject: Re: Micom 224+ problems
Message-ID: <403@mnetor.UUCP>
Date: Wed, 10-Apr-85 09:25:15 EST
Article-I.D.: mnetor.403
Posted: Wed Apr 10 09:25:15 1985
Date-Received: Wed, 10-Apr-85 11:18:03 EST
References: <306@linus.UUCP>
Reply-To: clewis@mnetor.UUCP (Chris Lewis)
Distribution: net
Organization: Computer X (CANADA) Ltd., Toronto, Ontario, Canada
Lines: 19
Xref: utcs net.dcom:920 net.bugs.uucp:461
Summary: 

We are encountering a very similar problem when our Pyramid (BSD4.2
uucp) trys to converse with System V's (VME10 and EXORmacs using
dialup or direct lines).  They *always* TIMEOUT.  We don't have this 
problem when conversing with other BSD4.2s.  I don't think that the 
"w"'s that you mention are directly related to the problem.  I think 
that this is an inconsistency between System V and BSD hangup 
sequences and the "w"'s are just a idiosyncracy of your lines 
(eg: they could be wrong baud rates from the other end).  Can 
anybody shed any light on this?  We would really appreciate it.

Our problem with the EXORmacs is considerably worse.  If our system
ends up in master mode at HUP time the dial-in line of the EXORmacs 
will hang with a uucico on it.  Killing the uucico brings up a "getty" 
which won't respond to keystrokes or "kill -9"'s.  I'm hoping that
fixing the TIMEOUT problem will fix this too.
-- 
Chris Lewis, Computer X (CANADA) Ltd.
UUCP: {allegra, linus, ihnp4}!utzoo!mnetor!clewis
BELL: (416)-475-1300 ext. 321