On Fri, 09 Sep 2011 07:28:17 -0400, DJW (Daniel) wrote:
> > 3) NFS file locking service fails to start. I haven't messed with
> > it at all. The recent update (marked stable meanwhile with 0 karma)
> > mentions enabling it by default. It also mentions SELinux issues,
> > but then it should NOT be marked stable prior to fixing the SELinux
> > issues. Permissive mode, btw, doesn't manage to start the service
> > either. What's up?
> >
> I believe the SELinux issues were caused by systemd not labeling the
> socket file that it was creating correctly. But this is supposed to be
> fixed in systemd-35-1.fc16.x86_64
# rpm -qa systemd selinux-policy\*
selinux-policy-3.10.0-25.fc16.noarch
systemd-35-1.fc16.x86_64
selinux-policy-targeted-3.10.0-25.fc16.noarch
# setenforce 0
# systemctl start nfs-lock.service
Job failed. See system logs and 'systemctl status' for details.
# systemctl status nfs-lock.service
nfs-lock.service - NFS file locking service.
Loaded: loaded (/lib/systemd/system/nfs-lock.service; enabled)
Active: failed since Fri, 09 Sep 2011 13:36:23 +0200; 12s ago
Process: 3860 ExecStart=/sbin/rpc.statd $STATDARG (code=exited, status=1/FAILURE)
Process: 3857 ExecStartPre=/usr/lib/nfs-utils/scripts/nfs-lock.preconfig (code=exited, status=0/SUCCESS)
CGroup: name=systemd:/system/nfs-lock.service
Oh, and more breakage:
# q
bash: q: command not found...
Failed to search for file: Process /lib64/dbus-1/dbus-daemon-launch-helper received signal 11
--
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
