Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 UW 5/3/83; site uw-june
Path: utzoo!watmath!clyde!cbosgd!ihnp4!houxm!vax135!cornell!uw-beaver!uw-june!dragon
From: dragon@uw-june (Brian Matthews)
Newsgroups: net.unix-wizards,net.micro.68k
Subject: Re: UUCP, serial port, and ExorMacs wierdness
Message-ID: <85@uw-june>
Date: Fri, 17-May-85 23:51:40 EDT
Article-I.D.: uw-june.85
Posted: Fri May 17 23:51:40 1985
Date-Received: Sun, 19-May-85 00:00:00 EDT
References: <78@uw-june> <604@mnetor.UUCP>
Organization: U of Washington Computer Science
Lines: 20
Xref: watmath net.unix-wizards:13233 net.micro.68k:779

Well, after some experimentation, I have some more info.  It seems that
if the calling uucico is uucp 5.2, it hangs the port, no matter what
the answering uucp is on the ExorMacs.  I compared the code of the SysV
uucico and the 5.2 uucico, and changed what looked like important
differences, and it worked!  Sort of.  The uucico now ALWAYS reports a
timeout (running it with -x4) after it has sent the final "OO 0", but
the uucico on the other end doesn't hang, it exits, and a normal getty
is spawned.  Unfortunately, after a number transfers, init seems to
break, and any process created is made a zombie when it exits!
We have been in contact with MicroSystems, and they're looking into the
problem, but I'd appreciate any help anyone else can give.

Brian Matthews
...uw-beaver!ssc-vax!cxsea!arrakis!blm

PS:  The code I modified was in cico.c, where things are coming to and
end.  There is an 'if (!setjmp(jmpbuf)) {'.  In this block is something
like 'omsg ("OOOOO 0", Ofn)' or something.  It is this statement I
removed.  Sorry I can't be more exact, but I'm typing this on a
different machine.  If it matters I can look it up.