After updating to autofs-5.0.8-19.8.1.x86_64, I find my NFS mounts are no longer available via autofs. I have two NFS shares on my network. Both can be mounted manually (mount -t nfs server:/path). Previously, both could also be accessed on /net using autofs (using the "/net -hosts" entry in auto.master). After the update, I now get "No such file or directory" under /net (on the client).
Also, I notice if I issue "service autofs status", I get
Mar 19 21:53:37 gregpad automount[15428]: lookup_init:136: lookup(yp): map auto.master: Local domain name not set
Mar 19 21:53:37 gregpad systemd[1]: Started Automounts filesystems on demand.
Mar 19 21:53:39 gregpad automount[15428]: get_exports: lookup(hosts): exports lookup failed for naspad
Mar 19 21:53:39 gregpad automount[15428]: key "naspad" not found in map source(s).
(gregpad is the name of the client; naspad is the name of one of the servers which has an NFS share). I don't know if this was happening before the update.
Currently, I have NIS (yp) installed but it's not enabled. /etc/hosts lists the client and server, and this setup seems to work for other commands (e.g., mount, showmount).
Thanks in advance for your insight/ideas!
Also, I notice if I issue "service autofs status", I get
Mar 19 21:53:37 gregpad automount[15428]: lookup_init:136: lookup(yp): map auto.master: Local domain name not set
Mar 19 21:53:37 gregpad systemd[1]: Started Automounts filesystems on demand.
Mar 19 21:53:39 gregpad automount[15428]: get_exports: lookup(hosts): exports lookup failed for naspad
Mar 19 21:53:39 gregpad automount[15428]: key "naspad" not found in map source(s).
(gregpad is the name of the client; naspad is the name of one of the servers which has an NFS share). I don't know if this was happening before the update.
Currently, I have NIS (yp) installed but it's not enabled. /etc/hosts lists the client and server, and this setup seems to work for other commands (e.g., mount, showmount).
Thanks in advance for your insight/ideas!