Here's a link to the unlink() documentation page:
http://publib.boulder.ibm.com/iseries/v5r2/ic2928/index.htm?info/apis/unlink.htm
Review the authority section for Figure 1-77. Authorization Required for unlink() (excluding QSYS.LIB, independent ASP QSYS.LIB, QDLS and QOPT)
-Eric
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of James Lampert
Sent: Thursday, August 11, 2011 4:19 PM
To: Midrange Systems Technical Discussion
Subject: Re: Strange behavior from unlink() Unix-type API
DeLong, Eric wrote:
Hmm, I'm thinking there might need to be RW authority to all
directories in the path. Something like that...
So far as I'm aware, there already is.
And there aren't any softlinks.
Some time ago, I added a call to fchown(), immediately after file
creation, to transfer ownership of the file to the user's primary group
profile, in order to prevent the file from disappearing if some
less-than-brilliant administrator did a DLTUSRPRF with OWNOBJOPT(*DLT)
on the creator (it's happened, believe me!)
At the moment, the best hypothesis I can come up with for explaining why
the owner is *explicitly* excluded from all *object* authority to the
file, in the affected environment, is that somehow the fchown() is going
terribly wrong.
Anybody ever hear of such a thing?
--
James H. H. Lampert
Touchtone Corporation
http://www.hbquik.com/jamesl
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/midrange-l.
midrange.com
