Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 5/3/83; site umcp-cs.UUCP
Path: utzoo!linus!philabs!seismo!rlgvax!cvl!umcp-cs!chris
From: chris@umcp-cs.UUCP
Newsgroups: net.bugs.uucp
Subject: Re: Bug in 4.2 UUXQT
Message-ID: <4775@umcp-cs.UUCP>
Date: Mon, 16-Jan-84 03:33:48 EST
Article-I.D.: umcp-cs.4775
Posted: Mon Jan 16 03:33:48 1984
Date-Received: Tue, 17-Jan-84 02:22:03 EST
References: <1714@tektronix.UUCP> <1552@rlgvax.UUCP>
Organization: Univ. of Maryland, Computer Science Dept.
Lines: 20

The solution should really be applied from the other side: after all,
each C. control file delineates one "set" of work to be done.  If all
files required by the "C." file are not present, uucico should send
none of them.  The code would have to go into cntrl.c and simulate
the code in uuxqt that makes sure that all required files are present.
If not, the C. file cannot yet be completed and should be left alone.
Unfortunately merely changing cntrl.c to do this is not sufficient,
because then uucico could loop forever noticing control files which
do not have all required data files, skipping them, and then rereading
the work directory.

Another solution would be to immediately delete the control file if
not all its required files are present; I think this would not harm
anything as it stands now, but would prevent an enhancement by which
one site could relay work requests to another.  As this poses interesting
security problems that might not be a bad idea anyway!
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci
UUCP:	{seismo,allegra,brl-bmd}!umcp-cs!chris
CSNet:	chris@umcp-cs		ARPA:	chris.umcp-cs@CSNet-Relay