SCIENTIFIC-LINUX-USERS Archives

September 2015

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender:
Mailing list for Scientific Linux users worldwide <[log in to unmask]>
Date:
Fri, 4 Sep 2015 15:43:30 -0500
Reply-To:
"~Stack~" <[log in to unmask]>
Message-ID:
Subject:
From:
"~Stack~" <[log in to unmask]>
Content-Type:
multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="Glj6ShVHgKF32oaFIk9W3c2m6VrG6T135"
In-Reply-To:
MIME-Version:
1.0
Comments:
Parts/Attachments:
text/plain (468 bytes) , signature.asc (834 bytes)
Greetings,

Just a follow up.

I never found a way to track the "why" behind a user getting permissions
when they were not supposed to. However, it appears that Panasas enabled
a new form of ACL's in their 5.5 update which we went to a few months
back. The ACL's are apparently always on and enabled outside of the
Linux permission scope. This is how users are getting permissions.

Thanks for all of the off-list suggestions people sent me. I do
appreciate all of the help.

~Stack~



ATOM RSS1 RSS2