On Sat, 2003-01-11 at 12:49, Mike wrote:
> Putting a quick and dirty fix to disregard anything after a '\ ' fixed that in
> my case.
Obviously that's not the real fix, since it precludes names with quoted
spaces. The bug is presumably in auto.net, since it shouldn't be
generating '\ ' if it really wants a continuation.
What does your auto.net look like?
> The next problem when dealing with multiline entries is everything attempts to
> mount itself. Granted it's unmounted immediately when it's not used, but going
> into /fs2/nfshomes/user when there at 75 entries in the nfshomes line tends to
> have a bit of overhead. It appears that when 'cd /fs2/nfshomes/toaster' is
> processed, the entire multiline for nfshomes is passed to the parse_mount in
> the sun module and everything gets mounted. Would it be possible to put some
> logic in place so that only the final directory that one cares about gets
> mountes?
Not really. autofs only sees lookups at its mountpoint level (ie, /fs2
in your case). I guess if nfshomes isn't mounted from the NFS server,
it could also trigger at that level, but the common case where the
exports are dir and dir/subdir, once you mount dir, it can't trigger on
any lookups under there (that's effectively a direct mount).
Perhaps you could modify your auto.net and your autofs setup, so that
nfshomes is the autofs mountpoint, and each home dir is treated as a
separate key?
J
_______________________________________________
autofs mailing list
[EMAIL PROTECTED]
http://linux.kernel.org/mailman/listinfo/autofs
