| Title: | system management communications forum |
| Moderator: | CHEST::THOMPSON |
| Created: | Fri Mar 21 1986 |
| Last Modified: | Thu Jul 08 1993 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 490 |
| Total number of notes: | 2018 |
When using an APPENV-generated environment on FUTURS I get a strange
problem which I am sure never used to happen before VMS V5.4
If, when logged into my own account, I try to create a file in one of
the application directorys, using an editor, a CREATE/ACL or even just
a straight CREATE, it puts a strange ACL on the beginning, for
example...
CSB> cre odw$$d_dat:a.a
Exit
CSB> dir/sec odw$$d_dat:a.a
Directory DISK$DATA2:[ODW010.DAT]
A.A;1 ODW (RWE,RWE,,)
(IDENTIFIER=[SDE,BARKER],OPTIONS=NOPROPAGATE,ACCESS=READ+WRITE+
EXECUTE+CONTROL)
(IDENTIFIER=ODW,ACCESS=READ+WRITE+EXECUTE+DELETE+CONTROL)
Total of 1 file.
CSB>
It does not, as you see, give me the right to delete the file ( or,
therefore to rename or supercede it ). The only solution is to go in
and change the ACL, using the ACL editor, and then delete it.
can anybody tell me
- Why it creates this extra ACL
- What can I do to stop it
- Is everybody else having this problem, or is it that they are all
just smarter than me ?
Chris
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 443.1 | CURRNT::ALFORD | An elephant is a mouse with an operating system | Wed Oct 16 1991 17:04 | 45 | |
Chris,
>>>>
A.A;1 ODW (RWE,RWE,,)
(IDENTIFIER=[SDE,BARKER],OPTIONS=NOPROPAGATE,ACCESS=READ+WRITE+
EXECUTE+CONTROL)
(IDENTIFIER=ODW,ACCESS=READ+WRITE+EXECUTE+DELETE+CONTROL)
CSB>
It does not, as you see, give me the right to delete the file ( or,
therefore to rename or supercede it ). The only solution is to go in
and change the ACL, using the ACL editor, and then delete it.
can anybody tell me
- Why it creates this extra ACL
- What can I do to stop it
- Is everybody else having this problem, or is it that they are all
just smarter than me ?
>>>>
This is not a feature of 5.4 This has always happened since 5.0
The "cure" is to put a default protection of O:RWED on the *TOP* directory of
the application.
This stops this idiocy.
I think you will find that your top directory only has O:RWE hence the missing
DELETE on the ACE.
Example:
$DIR [000000]FAC010/SEC
FAC010.DIR [FAC] (RWE,RWE,,)
.
.
.
(DEFAULT_PROTECTION, SYSTEM:RWED,OWNER:RWED,GROUP:,WORLD:)
| |||||