I must have come down with a bad case of exploratory dumba$$ this
morning. I inadvertently enabled the CentOS-plus repo and promptly
installed their kernel-2.6.18-194.26.1.el5.centos.plus.x86_64.rpm. Upon
reboot I discovered to my dismay that several services no longer worked,
including NFS. I
Robert G. (Doc) Savage wrote:
# service nfs start
Starting NFS services: [
OK ]
Starting NFS quotas: rpc.rquotad: error while loading shared
libraries: libwrap.so.0: failed to map segment from shared
object:
On Sun, Nov 28, 2010 at 11:48 AM, Trevor Hemsley
trevor.hems...@codefarm.com wrote:
Robert G. (Doc) Savage wrote:
# service nfs start
Starting NFS services: [
OK ]
Starting NFS quotas: rpc.rquotad: error while loading shared
On Sun, Nov 28, 2010 at 11:48 AM, Trevor Hemsley
trevor.hems...@codefarm.com wrote:
Robert G. (Doc) Savage wrote:
# service nfs start
Starting NFS services: [
OK ]
Starting NFS quotas: rpc.rquotad: error while loading shared
On Sun, 2010-11-28 at 19:48 +, Trevor Hemsley wrote:
Robert G. (Doc) Savage wrote:
# service nfs start
Starting NFS services: [
OK ]
Starting NFS quotas: rpc.rquotad: error while loading shared
libraries:
On Sun, Nov 28, 2010 at 4:01 PM, Robert G. (Doc) Savage
dsav...@peaknet.net wrote:
That may have been it. At least most of it. I did have selinux set to
permissive, and the CentOS-plus kernel installation must have quietly
set it back to enforcing. Not nice.
You are mistaken here :(
The
On Sun, 2010-11-28 at 16:44 -0800, Akemi Yagi wrote:
On Sun, Nov 28, 2010 at 4:01 PM, Robert G. (Doc) Savage
dsav...@peaknet.net wrote:
That may have been it. At least most of it. I did have selinux set to
permissive, and the CentOS-plus kernel installation must have quietly
set it back
On Sun, Nov 28, 2010 at 17:57, Robert G. (Doc) Savage
dsav...@peaknet.net wrote:
On Sun, 2010-11-28 at 16:44 -0800, Akemi Yagi wrote:
On Sun, Nov 28, 2010 at 4:01 PM, Robert G. (Doc) Savage
dsav...@peaknet.net wrote:
That may have been it. At least most of it. I did have selinux set to
Robert G. (Doc) Savage wrote:
If this is so, shouldn't I have been able to back out cleanly?
A more likely candidate is that selinux-policy was updated a couple of
weeks ago. That RPM owns /etc/sysconfig/selinux
--
Trevor Hemsley
Infrastructure Engineer
