Ian Kent <[EMAIL PROTECTED]> writes: > On Wed, 2007-08-01 at 15:13 +0200, Lukas Kolbe wrote: >> Hi Ian, >> >> > > figaro:/users/xxx /homes/xxx nfs >> > > rw,nosuid,vers=3,rsize=32768,wsize=32768,hard,intr,proto=tcp,timeo=600,retrans=2,sec=sys,addr=figaro >> > > 0 0 >> > > bongossi:/export/yyy /homes/yyy nfs >> > > rw,nosuid,vers=3,rsize=1048576,wsize=1048576,hard,intr,proto=tcp,timeo=600,retrans=2,sec=sys,addr=bongossi >> > > 0 0 >> > > >> > > where figaro only exports nfs v3, bongossi exports both v4 and v3 and we >> > > really would like to use v4. >> > >> > Actually, a multi map entry in the master map would probably work. >> > Initially I missed this out of version 5 (by accident) so you'll need >> > the patch on kernel.org that adds it. In fact I'd recommend applying all >> > the 5.0.2 patches. >> > >> > So forget the last suggestion and patch and apply all the 5.0.2 patches >> > on kernel.org and try a line in the master map like: >> >> Ok, done that :). >> >> > /homes multi yp auto_homes >> > -fstype=nfs4,nosuid,grpid,nobrowse,proto=tcp,port=2049 -- \ >> > yp auto_homes >> > -fstype=nfs,nosuid,grpid,nobrowse,proto=tcp,port=2049 >> > >> > and see if that gets what you need. The nfs4 one needs to be first >> > because the v4 servers provide both v4 and v3. >> >> This only gives me the nfs4 mounts, it seems like the second part of the >> multimount is not evaluated when the first one says "I don't have that >> directory you asked me about": > > Aaah yes, of course, sorry about that. > That would be because the first encountered key is used to decide pass > or fail.
No, it is because the second key was never added to the cache. See my earlier, somewhat cryptic message on this. As Pete said, if the default should be nfs4, that should happen in mount. -Jeff _______________________________________________ autofs mailing list [email protected] http://linux.kernel.org/mailman/listinfo/autofs
