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

[James Lampert <jamesl@xxxxxxxxxxxxxxxxx>]

Jack Kingsley wrote:
> James do you have to be running this under a specific profile in order for
> the results to turn out the way you want them to.

No.

While I haven't yet had time to get the fchown() call to a state where I 
can debug it (hopefully that will happen later today), I've established 
the following pattern:

In our development environment, the IFS objects' ownership is 
transferred, immediately on creation, to the owner's primary group 
profile, which is as it should be, with full authority granted to 
*PUBLIC, with nobody explicitly locked out of it.

In our production environment, the IFS objects' ownership remains with 
the creating user profile, and that creating user profile is then 
explicitly locked out of all object authorities to it, while *PUBLIC 
still *has* all object authorities to it, with the result that the 
creator/owner (and apparently *only* the creator/owner) is locked out of 
deletion, whether from the command line, or from WRKLNK, or from the 
unlink() API call.

And this seems to be happening regardless of who the creating user 
happens to be.

Hopefully, I'll know more before quitting time today.

--
JHHL