Path: utzoo!attcan!uunet!peregrine!elroy!ames!mailrus!uflorida!ukma!tut.cis.ohio-state.edu!osu-cis!att!oucsace!pmech
From: pmech@oucsace.cs.OHIOU.EDU (Paul J. Mech)
Newsgroups: comp.unix.wizards
Subject: Re: using System V 'cu'
Summary: A bit easier on the PATH ...
Message-ID: <364@oucsace.cs.OHIOU.EDU>
Date: 22 Nov 88 04:18:26 GMT
References: <6808@venera.isi.edu> <138@minya.UUCP>
Organization: Ohio University CS Dept., Athens
Lines: 18

In article <138@minya.UUCP>, jc@minya.UUCP (John Chambers) writes:
- In article <6808@venera.isi.edu>, cracraft@venera.isi.edu (Stuart Cracraft) writes:
- > How do you slow down cu's file transfer capability (e.g. the tilde-put
- > command) ??
- > 
- I've been bitten by this one on several systems.  What I've done is 
- write my own version of cat (typically 10 lines or so) that runs quite
- slowly, typically by reading 100-byte chunks, writing them, and then
- doing sleep(1).  I make a script called "cu" that has this "cat" in
- its search path before /bin, and knows the name of the real cu.  It
- seems to work pretty well.
- 
A simular technique that I use is a C program that metes out characters with
any number of delay schemes using fflush(), sleep(), and optional characters
in the file to flag additional delays. I use this as a filter with the ~$
command. It was a quick and dirty workaround to transfer a file to an IBM
mainframe that didn't seem to like me at all, but has prooven to be of enough
utility to keep around.