Re: Strange behavior from unlink() Unix-type API

[James Lampert <jamesl@xxxxxxxxxxxxxxxxx>]

DeLong, Eric wrote:
> James, did you ever read the link that I posted earlier?  I suspect
> you're still NOT checking the directories in the path that precede
> your file object.  EACH of the directories in your path MUST have at
> minimum *X, the directory that contains your file must have *WX, and
> the file object itself must all *OBJEXIST authority...

Uh, (1) the directories that always behaved properly were direct 
sister-directories to the one that was malfunctioning, i.e., in the same 
immediate parent directory, so path could not have been involved, and 
(2) in the malfunctioning directory, the owners of all files created 
after it began malfunctioning were explicitly locked out of object 
authorities for their files, and (3) the malfunctioning directory had no 
authority line at all for the owner, and as soon as I added one, it 
started behaving properly.

The only question remaining is how the owner's authority line for the 
malfunctioning directory disappeared in the first place, and why its 
absence would cause everything created therein to be created with an 
owner authority line explicitly locking out the owner's object authorities.

--
JHHL