×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
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
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
