Path: utzoo!attcan!uunet!cs.utexas.edu!sun-barr!olivea!orc!inews!iwarp.intel.com!gargoyle!chinet!les
From: les@chinet.chi.il.us (Leslie Mikesell)
Newsgroups: comp.unix.misc
Subject: Re: crc as child of cu
Message-ID: <1990Oct28.024119.7781@chinet.chi.il.us>
Date: 28 Oct 90 02:41:19 GMT
References: <554@lrark.UUCP>
Distribution: na
Organization: Chinet - Public Access UNIX
Lines: 24

In article <554@lrark.UUCP> gars@lrark.UUCP (Gary Smith) writes:
  
> I have 'crc' on my system (Microport SysV/AT {before reorganization}).
> 'crc' is the xmodem send/recieve program with no attendant support like
> you find in Pcomm or Xcomm.
>  
> The question is: How do I make 'crc' a child process of 'cu' ?

You probably can't make it work.  Cu forks and runs as 2 processes, one
reading the remote tty line and writing to the invoking terminal and
the other reading the terminal and writing to the remote.  During the
 ~$command escapes, the process reading the remote tty line stays active
which will screw up any file transfers that another program might
attempt over the same line.  I've been told that there is a compile option
in the cu source that can enable a variation of the shell command that
will kill the reading process, but I doubt if that helps you any more
than it did me.

On approach that will work is to use kermit to dial out, then use
a shell escape with explicit redirection of both stdin and stdout
to the remote tty line.

Les Mikesell
  les@chinet.chi.il.us