Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!bcm!dimacs.rutgers.edu!seismo!uunet!mcsun!ukc!vision!chris
From: chris@vision.uucp (Chris Davies)
Newsgroups: comp.mail.uucp
Subject: Re: usage of "ct"  (BNU of UUCP)
Keywords: UUCP, BNU, modem control, callback
Message-ID: <1991Feb1.135606.19910@vision.uucp>
Date: 1 Feb 91 13:56:06 GMT
References: <594@guug.guug.de> <8414@mgweed.UUCP>
Reply-To: chris@vision.UUCP (Chris Davies)
Organization: VisionWare Ltd., Leeds, UK
Lines: 19

In article <8414@mgweed.UUCP> prg@mgweed.UUCP (Gunsul) writes:
>The only other problem I've had with "ct" is it appears as though you can NOT
>run a uugetty on the "out-bound" port of the computer that is CALLING you.
>The outbound port should be just that, outbound only..  Running a uugetty on
>this port will do STRANGE things, like drop the session shortly after you
>connect and hit a few returns..

That's right.  It's because _c_t spawns a normal _g_e_t_t_y (which in turn starts
_l_o_g_i_n), and _g_e_t_t_y doesn't understand the locking mechanism used by _u_u_g_e_t_t_y and
_c_u to control access to the serial port.

It's a known problem, but I don't think anyone's done anything about it..

Chris
-- 
VISIONWARE LTD         | UK: chris@vision.uucp    JANET: chris%vision.uucp@ukc
57 Cardigan Lane       | US: chris@vware.mn.org   BANGNET: ...!ukc!vision!chris
LEEDS LS4 2LE, England | VOICE:  +44 532 788858   FAX:  +44 532 304676
-------------- "VisionWare:   The home of DOS/UNIX/X integration" -------------