Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!lll-lcc!pyramid!ncc!lyndon
From: lyndon@ncc.UUCP
Newsgroups: comp.os.minix
Subject: Re: How uucp handles incoming files
Message-ID: <1389@ncc.UUCP>
Date: Sun, 12-Apr-87 02:10:02 EST
Article-I.D.: ncc.1389
Posted: Sun Apr 12 02:10:02 1987
Date-Received: Sun, 12-Apr-87 19:44:07 EST
References: <480@gouldsd.UUCP> <43183@beno.seismo.CSS.GOV> <5897@ism780c.UUCP>
Distribution: comp
Organization: Nexus Computing Corp.,  Edmonton, AB
Lines: 21

In article <5897@ism780c.UUCP>, tim@ism780c.UUCP (Tim Smith) writes:
> > This involves only a rename of the file (not a copy) which is
> > generally quite efficient under Unix.
> 
> But a busy system will often keep the spool directory and the user
> directories on different file systems.  A rename then involves a
> copy.  I suspect that this is more common then having them on
> the same file.

MOST systems keep the spool and user partitions seperate.

Check your uucp logs and count the number of commands versus
the number of uucp's to a location off the spool partition.
I don't have exact numbers in front of me, but based on my
experience with uucp, 95+% of the files never leave /usr/spool/uucp.
On ncc, the breakdown is roughly 80% rmail, 15% rnews, with the
remainder being uucp's. Of the uucp commands, at least 90% of
those wind up in /usr/spool/uucppublic (in the spooling partition).

Anyway, if this *really* bothers you, modify the code to
fork a child process to do the copy and delete.