Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!pacbell.com!ucsd!nosc!humu!pegasus!richard
From: richard@pegasus.com (Richard Foulk)
Newsgroups: comp.unix.sysv386
Subject: Re: Using cu with rz/sz?  Can't be done?
Message-ID: <1991May16.052500.27105@pegasus.com>
Date: 16 May 91 05:25:00 GMT
References: <677@genco.bungi.com> <240@sos.com> <1991May14.150241.1692@chinet.chi.il.us>
Organization: Pegasus,  Honolulu
Lines: 22

>
>Cu forks into 2 processes, one that reads the remote tty line and
>writes to the controlling terminal and one that reads the terminal
>line and writes to the remote.  Most versions leave the process
>reading the remote tty running during ~! or ~$ escapes so it is
>impossible to use any kind of file transfer protocol.  If you
>have kermit set up for dial-out on your system you can either
>use it's own native protocol or shell escape and redirect to
>the tty as mentioned above.
>

You may have to be root to connect another process to a port that
kermit already has open, to override the exclusive-open.

I think I have a patch around here somewhere that enables kermit to
fork other processes and connect them to the remote port without
encountering that problem.


Richard
-- 
Richard Foulk		richard@pegasus.com