Red Hat Bugzilla – Bug 637117
Fix nfs/rpcsvcgssd start priorities
Last modified: 2011-10-04 11:30:45 EDT
Created attachment 449392 [details]
Log output of systemctl restart nfs.service
Description of problem:
While I've been using nfs before I switched to systemd - I'm not able to start this service with systemd anymore.
Here is just something for 'linux systemd guru masters' which are probably able to decrypt the reason of nfs failure?
Version-Release number of selected component (if applicable):
Steps to Reproduce:
This is another case of a deadlock when starting of a service triggers a synchronous start of another one, but the latter has an After dependency on the first one.
Specifically here /etc/init.d/nfs does:
[ -x /usr/sbin/rpc.svcgssd ] && /sbin/service rpcsvcgssd start
And "systemctl show rpcsvcgssd.service" says:
After=... nfs.service ...
Usable workaround here seems to be:
SYSTEMCTL_SKIP_REDIRECT=1 /etc/init.d/nfs restart
If nfs has a unilateral dep on rpcsvcgssd such that it starts it always, it shouldn't have a chkconfig priority set earlier than rpcsvcgssd.
I'm starting nfs only when I need to use on my machine i.e. for kvm guest - there is no reason to run this service all the time or even have it available on demand.
> If nfs has a unilateral dep on rpcsvcgssd such that it starts it always, it
> shouldn't have a chkconfig priority set earlier than rpcsvcgssd
No. rpcsvcgssd is only need if the NFS server is exported
secure exports (i.e. exports with the 'sec=krb5:krb5i:krb5p' opts).
To enable the daemon one needs to set the SECURE_NFS=yes
Still, there's no reason for it to have a hardcoded later priority, if in the circumstances where it is needed, it is always needed before nfsd.
There are plans afoot to combined the client side daemon (rpc.gssd)
and the server side daemon (rpc.svcgssd) into one daemon. When
that happens (hopefully by f15) I'll remove the hard coded call
to rpc.svcgssd from the nfs start up script.