Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10 beta 3/9/83; site encore.UUCP Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!genrad!panda!talcott!encore!ptw From: ptw@encore.UUCP (P. Tucker Withington) Newsgroups: net.bugs.uucp Subject: Re: 4.2 uucp performance problems? Message-ID: <157@encore.UUCP> Date: Tue, 12-Feb-85 17:22:23 EST Article-I.D.: encore.157 Posted: Tue Feb 12 17:22:23 1985 Date-Received: Thu, 14-Feb-85 01:46:12 EST References: <1363@hao.UUCP> <3007@allegra.UUCP> <> <> <> Reply-To: ptw@encore.UUCP (P. Tucker Withington) Organization: Encore Computer Corp., Wellesley Hills, MA Lines: 20 Summary: >Here is the pkcget() trick. In the read loop, immediately after the >test to see if all the characters have been read has failed, add the >following line. > > nap((n * HZ * 10) / linebaudrate); /* n char times */ > Um, Peter, well I guess you have your own spiffy uucp, but in what comes off the 4.2 tape I *think* you want to say: nap(((n-nchar) * HZ * 10) / linebaudrate); /* char times */ to wait for the number of chars you still need (vs. the whole msg.) Yes? Admittedly the pkcget fix is kind of groaty already, but just to save anyone who charged off and plopped your line in verbatim... o.o --tucker ~ P.S. Since you gave the line away, I guess I'll give my 6 chars away too.