using System V 'cu'

Barry Shein bzs at encore.com
Sun Nov 20 03:41:50 AEST 1988


In reply James Logan suggests
>In article <6808 at venera.isi.edu> cracraft at venera.isi.edu (Stuart Cracraft) writes:
>>How do you slow down cu's file transfer capability (e.g. the tilde-put
>>command) ??
>
>There are two thing I can think of to try.  The first idea is to
>give the yourself a nice value of 39.  Just type 
>
>	nice -39 $SHELL

(this increases priority, beyond the max which is silly and may
actually do nothing, you also have to be super-user, but that's what
you meant?)

Sounds like a bad idea, this only operates on the process, not the
terminal handler, if nothing is competing for time it will have very
little effect if any, might even make things worse, it's just not the
process priority that's involved. The other idea also sounds like
poking around in the dark. If something is competing for processor
time it better be the process of a good personal friend :-)

Tip (bsd cu superset) has linedelay and chardelay, I guess cu doesn't,
you might consider just getting Kermit which is free, probably works
on your system and will solve this problem and provide reliable
transfer as well, CKermit is very nice (-19) and worth putting up.

If that can't work I'd either slow down the baud rate on the sending
side if possible or look at the NLDELAY parameters in termio(7) and
stty(1), maybe just before you start a try '~!stty nl1 cr1 < /dev/outputty'
or some such thing and see if that takes, not sure if cu resets line
parameters at magical times.

Your problem is you're trying to kludge around a real problem the old
cu doesn't address adequately, period. I recommend something like
Kermit, cu is really old and simple-minded.

	-Barry Shein, ||Encore||



More information about the Comp.unix.wizards mailing list