1833730 Members
2373 Online
110063 Solutions
New Discussion

Swacl and the + sign

 
Gary Stewart_3
Occasional Contributor

Swacl and the + sign

I have searched everywhere I know of and can't find this answer. I know the +
sign on the end of the permissions has to do with swacls. WHAT does it have to
do with it. WHAT effect does it have on the files and HOW, if possible do I get
rid of it? DOES it affect doing compiles in C++ or any other programming
language?
Where can I find info on this.

Thanks
2 REPLIES 2
Alan Riggs_1
Regular Advisor

Re: Swacl and the + sign

The "+" displayed with permissions when doing an ll (ls -l) simply indicates
that optional acl are attached to the file in question. These acl entries can
be displayed with lsacl and changed with chacl (see men pages for each
command). ACLs control access fo tiles. They are an additional and more
finely tuned manner of restricting access to files than the standard ugo
permissions. My understanding is that ACLs are not supported on JFS file
systems. You can create acl entries on LFS files, but my experience has been
that the entries do not survive any lvm work on the file system/logical volume
in question.

Of themselves, ACLs should have no effect upon compilation. But since ACLs
restrict who ohas access to files, the specific permissions might be
interfering with compiler access to necessary files.
Zhang Zhao gui
Frequent Advisor

Re: Swacl and the + sign

I also encountered the similar problem when I did a remote "swinstall", I got
"swacl: No permission"
I believed it has nothing to do with "+" in the output of "ll". But how can I
solve my swacl permission problem?