http://bugzilla.suse.com/show_bug.cgi?id=1150807
http://bugzilla.suse.com/show_bug.cgi?id=1150807#c3
Neil Brown changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |yast2-maintainers@suse.de
Flags| |needinfo?(yast2-maintainers
| |@suse.de)
--- Comment #3 from Neil Brown ---
yast shouldn't encode a dependency on nfsidmap - that is that job of that
package management - not yast.
libnfsidmap has been merged into nfs-utils, so there is no separate package any
more.
nfs.service is a legacy name. nfs-client.service is the name that upstream
uses and has been available for quite some time.
We recently removed the legacy names.
nfs-client runs client-side services.
nfs-server runs server-side services.
However it seems that yast still uses "nfs". I thought I had asked them to
change that.
The error message
rpc.idmapd: config error at /etc/nfs.conf:12: error loading included config
does not signify a fatal error. You can silence it by creating
/etc/nfs.conf.local as an empty file. I'll get that sorted out in the next
update.
If you
systemctl start nfs-client
and the
mount -a
does the NFS get mounted properly?
yast2-maintaineres: can the dependecy on nfsidmap be removed, and the service
names be changed to nfs-client and nfs-server?
Also the old nfs-client script mounted NFS filesystems, while the new
nfs-client service doesn't do that. So after adding things to /etc/fstab, yast
would need to "mount -a -t nfs" or similar. (this was discussed in Bug 1006815
)
--
You are receiving this mail because:
You are on the CC list for the bug.