smk@axiom.UUCP (Steven Kramer) (01/18/84)
Methinks there a bug in the 4.2BSD uucp where if files on the remote side
are not copied because of ACCESS DENIED (due to not being able to
write into the directory), the file is NOT put into ~uccp! A user
here got burned because of that. Is there a fix? (I imagine the
fix is simple, but LOCATING the place in uucp is always a chore.)
--
--steve kramer
{allegra,genrad,ihnp4,utzoo,philabs,uw-beaver}!linus!axiom!smk (UUCP)
linus!axiom!smk@mitre-bedford (MIL)guy@rlgvax.UUCP (Guy Harris) (01/22/84)
Well, the code to do this is in "cntrl.c"; the routine which does it is
called "putinpub". A look at the code that would call "putinpub" seems
to indicate that it does all its access checking before it even receives
the file. It calls "chkpth" which checks what the USERFILE allows, and
calls "chkperm" which checks that the file and the containing directory are
both publicly writable (both these are in "chkpth.c"). So it looks like
the only way the program would stick things into PUBDIR is if the "xmv"
failed *but* the permissions at the time the transfer started were valid.
I suspect this isn't a bug, but either a feature or a misfeature (depending
on your point of view).
Guy Harris
{seismo,ihnp4,allegra}!rlgvax!guy