On Tue, 2007-09-11 at 10:55 -0700, Simon Gao wrote: > Ian Kent wrote: > > On Tue, 2007-09-11 at 16:46 +0930, Shane wrote: > > > >> Hey All, > >> > >> I'm trying to get a "top-level" automount to work. eg > >> > >> /home -rw,vers=3,fstype=nfs,intr,hard,tcp,rsize=32768,wsize=32768 > >> srv1:/export/home/ > >> > >> I've tried a few things so far - putting that exactly as is into > >> /etc/auto.master, created an auto.direct file and put /- auto.direct > >> into auto.master neither any joy - also tried /home auto.home in > >> auto.master and above but with * or / as the key as contents of > >> auto.home none are working. > >> > > > > Not valid in auto.master. > > > > An indirect map must have keys that are a directory component only, that > > is no "/"s. > > > > So, in auto.master you can have: > > > > /home auto.home > > > > and auto.home as: > > > > * srv1:/export/home/& > > > > to mount /home/myname as srv1:/export/home/myname > > > > You could leave out the "&" but I'm not sure that would be useful. > > > > > >> Firstly is this actually possible? Though I have no idea how Apple > >> translate our maps into something automount uses they do get around > >> this but /home is a symlink to somewhere like > >> /private/var/automount/home. If its possible ...what have I missed to > >> get this working? > >> > > > > No, not possible with version 4. > > > > Single level indirect maps aren't possible by definition. > > > > Single level direct maps are possible with version 5. > > > > So, in auto.master you could have: > > > > /- auto.home > > > > and auto.home: > > > > /home svr1:/export/home > > /other/dir other:/export/other > > > > and the like. > > > > Ian > > > > > > Is there a good way to set up ldap entries so autofs 4 and 5 can each > find and match its own version of automount maps?
The maps used with autofs v4 should all work with v5. If you find something that doesn't report it. > > Many times, one has to run different versions of Redhat distributions > and not able to migrate to RHEL5 all together. Yes, and the other problem is mixed OS environments. One goal of v5 is to be able to be able to "fit in" with other automount implementations, allowing a single set of map specifications. I think we're well along in this regard so if you find a case where this is broken report that too. Generally v4 maps need to include ldap information so this can't be achieved with mixed v4 and v5 setups. For example, in v4, you usually need something like: automountInformation: ldap://<server name>/ou=<map name>,<basedn> for all map entries. But in v5 it's generally best to use the map name only such as: automountInformation: <map name> and let the autofs work out the nsswitch source for the map. Ian _______________________________________________ autofs mailing list autofs@linux.kernel.org http://linux.kernel.org/mailman/listinfo/autofs
