From: Mark Valites <mvalites@buffalo.edu>
To: linux-nfs@vger.kernel.org
Subject: Re: RH 7 nfs-utils update causes segfault
Date: Mon, 07 Mar 2016 11:27:14 -0500 [thread overview]
Message-ID: <56DDABE2.3040204@buffalo.edu> (raw)
In-Reply-To: <alpine.OSX.2.19.9992.1603071059490.66950@dhcp0201.cthon.org>
On 03/07/2016 11:00 AM, Benjamin Coddington wrote:
> Hey Mark, could it be this one?
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1313090
>
> Ben
>
Doesn't look like it:
$ sudo restorecon -v /etc/krb5.keytab
<no output>
$ ls -laZ /etc/krb5.keytab
-rw-------. root root unconfined_u:object_r:krb5_keytab_t:s0
/etc/krb5.keytab
I'd only had selinux in permissive mode, so I tried disabling it as
well, but that too unfortunately made no difference.
next prev parent reply other threads:[~2016-03-07 16:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-07 15:48 RH 7 nfs-utils update causes Mark Valites
2016-03-07 16:00 ` Benjamin Coddington
2016-03-07 16:27 ` Mark Valites [this message]
2016-03-07 19:49 ` RH 7 nfs-utils update causes segfault Benjamin Coddington
2016-03-08 16:57 ` Mark Valites
2016-03-08 18:21 ` Benjamin Coddington
2016-03-08 18:39 ` Mark Valites
2016-03-08 19:07 ` Benjamin Coddington
2016-03-08 19:30 ` Mark Valites
2016-03-08 20:16 ` Benjamin Coddington
2016-03-08 20:27 ` Mark Valites
2016-03-08 20:37 ` Benjamin Coddington
2016-03-08 20:51 ` Mark Valites
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56DDABE2.3040204@buffalo.edu \
--to=mvalites@buffalo.edu \
--cc=linux-nfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox