[12621] in athena10
Re: [Debathena] #1370: AppArmor doesn't play nice with AFS
daemon@ATHENA.MIT.EDU (Debathena Trac)
Mon Jul 21 09:47:37 2014
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
From: "Debathena Trac" <debathena@MIT.EDU>
Cc: debathena@MIT.EDU
To: jdreed@MIT.EDU, andersk@MIT.EDU
Date: Mon, 21 Jul 2014 13:47:26 -0000
Reply-To:
Message-ID: <057.67913e5fcdba14e9a734e654996278c3@mit.edu>
In-Reply-To: <042.bd78f5941476aa8a1127287a99f0e40a@mit.edu>
Content-Transfer-Encoding: 8bit
#1370: AppArmor doesn't play nice with AFS
-----------------------+---------------------------------------
Reporter: jdreed | Owner:
Type: defect | Status: new
Priority: high | Milestone: The Distant Future
Component: -- | Resolution:
Keywords: | Fixed in version:
Upstream bug: |
-----------------------+---------------------------------------
Changes (by jdreed):
* milestone: Current Semester => The Distant Future
Comment:
I re-opened this same issue as #1508 (now closed as a dupe of this bug),
but that has a bit more info about the relevant syslogs. I think what I'd
like to see is OpenAFS complain loudly to syslog when it has to fall back
to the process credentials, so that at least it appears in the log and we
can differentiate real network failures from apparmor/selinux stupidity.
I'll note that apparmor-config 1.2.9 gives up and implements the
workaround that was suggested a year ago.
I haven't seen the telepathy failures recently, so I can't further debug
what is failing with a cwd of /.
--
Ticket URL: <https://athena10.mit.edu/trac/ticket/1370#comment:3>
Debathena <http://debathena.mit.edu>
MIT Debathena Project
