On 2019-09-13 14:51, Patrick Shanahan wrote:
that is good, but didn't not provide connection to my errant box. It appearently required a later/newer version of nfs-client.
It might be that some defaults changed with the version jump (e.g. server now requires NFSv4, but your client was configured to only try NFSv3 or something along those lines). I for one had an /etc/nfsmount.conf.rpmsave after the update, because I explicitly set Defaultvers=4, whereas in the replacement it was commented out.
Why is nfs-client a target and not a service and does it need to be enabled which is not the case on any of my Tw installs?
Most things on the client are handled by mount.nfs I believe. There isn't really any "daemon" or "service" to run. The unit file just specifies the dependencies with remote-fs{-pre}.target and pulls in the various gss services that are needed for kerberos. Someone please correct me if I'm off. Cheers -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org