net-fs/autofs-4.1.3-r7 fails to work on my new Thinkpad X60s, using gentoo-linux-2.6.19-r5. The init file runs without error, but nothing gets mounted, and --ghost fails to show any new directories. For comparison, autofs works perfectly with another gentoo machine on same network, with config files set up the same way.The new laptop does have a SATA hard drive and Intel dual-core processor.All the devices listed in /etc/autofs/auto.auto can otherwise be mounted normally as set in /etc/fstab. I don't know how to proceed further... Reproducible: Always Steps to Reproduce: 1./etc/init.d/autofs start 2. 3. Actual Results: # /etc/init.d/autofs start * Starting automounter ... /mnt/auto [ ok ] # mount shows only one new mounted item: automount(pid10010) on /mnt/auto type autofs (rw,fd=4,pgrp=10010,minproto=2,maxproto=4) Expected Results: new mounts to show for for boot, cdrom, and the network shares: data and media I'll provide any additional information upon request...
got the same error here. problem: autofs needs netmount. instead of 'need localmount' there should be something like 'need localmount netmount' in the init-script. But since 'netmount' itself only scans in '/etc/fstab' for NFS-mounts, 'portmap' will only be required if there're NFS-mounts there. So, real fix, 'netmount' should be expanded to check auto.* configs also and 'autofs' should depend on 'netmount'. quick help for you (and me, since I'm not the maintainer of autofs and netmount): 1. rc-update add portmap default 2. rc-update add netmount default
New maintainer, net-fs/autofs-5.0.3-r1 is now in the tree.
Seems a bit related with bug #163210. The comment I added there amounts to: I think it's the administrator's responsibility to install portmap/rpc.statd on machines that are going to mount nfs. The suggestion made here is that the maps are scanned when autofs is started. With autofs-4, that may have been the way to go, because it was the init script's responsability to initialize all mount points. With autofs-5, the daemon itself reads all the maps (whether they are on-disk, or acquired through nis or ldap, regardless of the map names). It is my gut-feeling that if you want nfs prepared automatically when necessary, a clean solution would be to associate the loading of the nfs-module with the starting of portmap and rpc.statd. But that's not my decision to make if this is to be a distribution-wide addition. All this is open for discussion of course...
The autofs init-script already contains: use ypbind nfs slapd portmap net So whenever one of these services is supposed to be started, it will be started before autofs. Enabling these services is the responsibility of the administrator. A comment in the ebuild also warns the administrator to enable portmap if nfs is to be used. Therefore closing this as fixed.
