* Patrick Shanahan [09-12-19 18:58]:

* Patrick Shanahan [09-12-19 18:47]:

...

what has happened to Tumbleweed nfs?

cannot run "yast nfs", complains These packages need to be installed: nfsidmap

but there is no nfsidmap, only nfsidmap-devel /usr/sbin/nfsidmap exists from nfs-client

systemctl restart nfs Failed to restart nfs.service: Unit nfs.service not found.

indeed, there is no /usr/lib/systemd/system/nfs.service, but: ls -la /etc/systemd/system/multi-user.target.wants/nfs.service yields: /etc/systemd/system/multi-user.target.wants/nfs.service -> /usr/lib/systemd/system/nfs.service

rpm -ql /usr/lib/systemd/system/nfs.service package /usr/lib/systemd/system/nfs.service is not installed

rpm -ql /etc/systemd/system/multi-user.target.wants/nfs.service package /etc/systemd/system/multi-user.target.wants/nfs.service is not installed

the generated mail "New Tumbleweed snapshot 20190909 released!" provides some insight, but ...

- Remove service aliases - these files are deleted. nfs.service nfsserver.service nfs-server.nfsserver.conf nfs-client.nfs.conf Now the upstream standard service names "nfs-client" and "nfs-server" must be used.

but "nfs-client" is a target, not a service

above "rpm -ql ..." is incorrect, s/b rpm -qf xxx and provides No such file or directory haven't been removed from locate.db

systemctl status nfs-client.target ● nfs-client.target - NFS client services Loaded: loaded (/usr/lib/systemd/system/nfs-client.target; disabled; vendor preset: disabled) Active: inactive (dead) shouldn't nfs-client be enabled if one previously had nfs enabled? -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org

* Peter Suetterlin [09-13-19 06:50]:

Patrick Shanahan wrote:

...

what has happened to Tumbleweed nfs?

Not sure. Just to add here, yesterday I had tried to set up my home computer with TW (new install on separate partition, old is 42.3), and I failed at getting the NFS server to run properly. I could mount via NFS locally (mount <myip>/export/dir /mnt), but doing so from another machine in the local net was refused without message in the log. (firewall was off).

So yes, something's fishy it seems. (see also the missing nfs.conf.local thread).

touch /etc/nfs.conf.local appears to satisfy the requirement in the client try starting nfs-client.target may also need being enabled for future needs. have no idea why it is a "target" rather than a "service". maybe someone knowledgable will comment .... for the most part, I have or appear to have nfs talking but have one box which cannot connect to a newer server. an old (42.2) still works, but it could not connect to a Tw server until I reconfigured the exports with yast on the Tw server. Didn't change anything but it then connected. ???? lots of questions w/o answers :( guess I missed the announcement ... -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org

Patrick Shanahan wrote:

I got the reluctant box nfs access finally. needed to update nfs-client, I believe. but why ????

Ah, I will check this tonight. Indeed my reluctant machine still has nfs-client-2.1.1, whereas recent is nfs-client-2.3.3. So might be some protocol mismatch? But I cannot say I like that. Also older clients should be able to connect, no? -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org

Patrick Shanahan wrote:

* Peter Suetterlin [09-13-19 12:42]:

...

Ah, I will check this tonight. Indeed my reluctant machine still has nfs-client-2.1.1, whereas recent is nfs-client-2.3.3. So might be some protocol mismatch?

But I cannot say I like that. Also older clients should be able to connect, no?

yes

So that sounds like a bug then. I just checked my machine at home that cannot mount from the new TW installation. Unfortunately upgrading nfs-client has a whole rats tail on dependencies, and I can't easily dup the machine - AFAIK the software I use it for doesn't run properly with the new TW ffmpeg stuff. And as that is my multimedia home center I don't really want to risk my evening leisure :o But I *can* confirm that I can mount the directory from the new TW machine w/o any problem from my laptop also running the most recent TW (i.e., also nfs-client-2.3.3). Not really sure if that is indication enough for a bug report. Some more confirmation would be nice... -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org

On 2019-09-13 13:52, Patrick Shanahan wrote:

* Peter Suetterlin [09-13-19 06:50]:

...

Patrick Shanahan wrote: (...) So yes, something's fishy it seems. (see also the missing nfs.conf.local thread).

touch /etc/nfs.conf.local appears to satisfy the requirement

Posted this already on opensuse-factory, but fits here as well: This was first introduced with commit [1], some time after the release of nfs-utils 2.1.1 (the previous version in Factory). The change finally made it to Factory with version 2.3.3 from snapshot 20190909. The configuration parser will now complain if an included file doesn't exist. Cheers [1] http://git.linux-nfs.org/?p=steved/nfs-utils.git;a=commit;h=9569237ba50c5857... -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org

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

Hi, [...]

With the info from your follow up email, the fact that multi-user.target wants a service file that no longer exists is also a bug worth reporting. (again for future reference)

besides that /etc/NetworkManager/dispatcher.d/nfs has to be modified, too. Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org