Comment # 21 on bug 990356 from jc sl

(In reply to Neil Brown from comment #20)
> > Out of curiosity, why is it started unconditionally?
> 
> Because it is not very easy to arrange for something to start conditionally
> in systemd when the condition is based on a config file.
> 
> It could be done with a "generator" to parse the config file and create a
> drop-in which modified the start-up behaviour of some service.  But that
> sort of complexity is best kept for when it is really needed.
> 
> On the other hand, I just wrote a generator to make sure nfs-server start-up
> was ordered properly w.r.t. various mount points becoming available. 
> Extending that to only make nfs-server only depend on rpc-statd when v2 or
> v3 is enabled would certainly be possible...
> 
> BTW kernel-default-4.7.0-2.2 should fix the delays.

Thanks for the explanation. It would be nice if it were started only when
needed, but I understand that maintenance is also quite important. If it
doesn't have side effects keeping it simple is better.

Back on the issue, after the kernel and related packages has been updated the
server doesn't start. I think that all comes from this error:

   nfs-config.service: Failed at step EXEC spawning
/usr/libexec/nfs-utils/nfs-utils_env.sh: No such file or directory

Indeed the file isn't there. zypper se -f nfs-utils_env.sh shows that the file
comes from nfs-client, but rpm -ql nfs-client says that the file is in
/usr/lib/systemd/scripts/nfs-utils_env.sh.

Greetings.