Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site allegra.UUCP
Path: utzoo!watmath!clyde!bonnie!akgua!whuxlm!whuxl!houxm!mhuxt!mhuxr!mhuxn!ihnp4!allegra!mp
From: mp@allegra.UUCP (Mark Plotnick)
Newsgroups: net.unix-wizards
Subject: how safe is it to read/write with fopen'ed files?
Message-ID: <4983@allegra.UUCP>
Date: Sun, 25-Aug-85 15:36:23 EDT
Article-I.D.: allegra.4983
Posted: Sun Aug 25 15:36:23 1985
Date-Received: Tue, 27-Aug-85 06:48:43 EDT
Organization: AT&T Bell Laboratories, Murray Hill
Lines: 13

Someone here discovered that you can speed up ethernet uucp transfers
('e' protocol in honey-danber uucp) by up to 2x by changing the
fread/fwrites in eio.c to read/writes.  They're still surrounded by
fopen/fclose, though, since cntrl.c wasn't touched.  Note that the
resulting reads and writes are the only routines called to do i/o here;
they aren't being intermixed with other freads, fwrites, putchars, or
anything like that.  Although this works OK under 4.2bsd and V8, I'm
wondering what will happen if we run the new uucp on systems such as
Ultrix and Sun, in which we can't examine the source code to
fopen/fflush/fclose.  Does anyone know if we could run into any
problems here?
	Mark Plotnick
	allegra!mp