On Tue, 2008-11-25 at 11:27 +0100, Ondrej Valousek wrote: > Ian, > So what is the conclusion in terms of NFSv4 compatibility? Will the > -hosts map work in autofs5?
I don't think so, not the hosts map, since the export path doesn't match the mount location path. There are other difficulties as well such as having to modify paths in the export list as we go. However, exports with "nohide" option should be automounted by the kernel client and not confuse autofs so that part is ok with 5.0.4 or if the patch which deals with this has been applied to 5.0.3. This is something I need to work on. > Thanks, > Ondrej > > Ian Kent wrote: > > On Mon, 2008-11-24 at 12:31 -0800, Bill Shannon wrote: > > > >> Peter Staubach wrote: > >> > >>> Bill, why aren't you using the -hosts map? > >>> > >> That's a good question... > >> > >> I don't remember how I got to this point, but ... > >> > >> I just tried using -hosts, but it doesn't seem to be working: > >> > >> vostro# cat /etc/auto.master > >> # $Id: auto.master,v 1.2 1997/10/06 21:52:03 hpa Exp $ > >> # Sample auto.master file > >> # Format of this file: > >> # mountpoint map options > >> # For details of the format look at autofs(8). > >> # /misc /etc/auto.misc --timeout=60 > >> /home /etc/auto.home -nosuid > >> #/net /etc/auto.net -nosuid > >> /net -hosts -nosuid > >> #/- /etc/auto.direct -nosuid > >> vostro# /etc/init.d/autofs reload > >> Reloading automounter: checking for changes ... > >> Reloading automounter map for: /home > >> Stopping automounter for: /smb > >> vostro# ls /net/nissan > >> ls: cannot access /net/nissan: No such file or directory > >> vostro# /etc/init.d/autofs restart > >> Stopping automounter: > >> Couldn't stop automount for /home done. > >> Starting automounter: > >> failed to start automount point /home > >> done. > >> vostro# /etc/init.d/autofs reload > >> Reloading automounter: checking for changes ... > >> Reloading automounter map for: /home > >> vostro# ls /net/nissan > >> ls: cannot access /net/nissan: No such file or directory > >> vostro# grep nissan /etc/hosts > >> 192.168.1.2 nissan > >> > >> I think that's the reason I ended up with an auto.net map, > >> although it now seems likely that it never worked as intended. > >> > >> I started chasing this problem because my auto.home map wasn't > >> working, which I now understand is the expected behavior based > >> on the way I'm now exporting my /export/home filesystems. My > >> mistake. > >> > >> I just fixed my auto.home map using multimounts. > >> > >> Still, any hints as to why the -hosts pseudo-map isn't working > >> would be appreciated. Are you sure it's *supposed* to work? > >> It's not documented in the man page. > >> > >> I think this is the version of autofs I have: > >> > >> vostro# dpkg-query -l 'autofs*' > >> Desired=Unknown/Install/Remove/Purge/Hold > >> | > >> Status=Not/Installed/Config-f/Unpacked/Failed-cfg/Half-inst/t-aWait/T-pend > >> |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: > >> uppercase=bad) > >> ||/ Name Version Description > >> +++-==============-==============-============================================ > >> ii autofs 4.1.4+debian-2 kernel-based automounter for Linux > >> > > > > Yep, that's version 4. > > > > > >> Is there an "autofs5" package I should install instead? > >> > > > > I'm not sure. > > > > There is an autofs5 in the package pool on the mirrors but I can't tell > > which release it belongs to. > > > > Perhaps an "apt-cache search" will give the answer. > > > > Ian > > > > > > _______________________________________________ > > autofs mailing list > > [email protected] > > http://linux.kernel.org/mailman/listinfo/autofs > > > _______________________________________________ autofs mailing list [email protected] http://linux.kernel.org/mailman/listinfo/autofs
