Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/18/84; site down.FUN Path: utzoo!watmath!clyde!cbosgd!ihnp4!mhuxn!mhuxm!mhuxi!mhuxh!mhuxv!mhuxt!mhuxr!ulysses!allegra!princeton!down!honey From: honey@down.FUN (code 101) Newsgroups: net.bugs.uucp Subject: Re: 4.2 uucp performance problems? Message-ID: <438@down.FUN> Date: Thu, 7-Feb-85 06:49:11 EST Article-I.D.: down.438 Posted: Thu Feb 7 06:49:11 1985 Date-Received: Fri, 8-Feb-85 03:28:28 EST References: <1363@hao.UUCP> <3007@allegra.UUCP> Organization: Princeton University, EECS Lines: 12 Summary: pkcget() speedup revealed 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 */ This assumes you set linebaudrate (or a similar variable) in fixline(), and that you have a nap call (or a similar function). I wish I didn't have to be so cagey about what I can and can't show here -- the line of code above belongs to me, not AT&T. Now it belongs to everyone. Peter