In Solaris Express b19, automount(1m) says in part
Server proximity takes priority in the selection process. In
the example above, if the server delta is on the same net-
work segment as the client, but the others are on different
network segments, then delta will be selected; the weighting
value is ignored. The weighting has effect only when select-
ing between servers with the same network proximity. The
automounter always selects the localhost over other servers
on the same network segment, regardless of weighting.
(I note with pleasure that's a bit more detailed and precise than in Solaris 9.)
Now, what I want to do on my laptop is this:
If it's reachable, mount my home directory from my fixed-location system
(however it may be able to get to it, as long as the name remains
constant). If not, mount a minimal local copy, which I'd typically set my
own synchronization up (using a script with rsync or whatever, presumably
run frequently off cron but only doing any real work if both were
accessible but a single flag file's timestamp was newer on the local copy)
for certain limited subdirectories and dot-files, confined to
things that wouldn't likely get updated both places at once, like
$HOME/.dt/`uname -n|sed -e 's/\.*//'`:* contents.
But the parts "Server proximity takes priority..." and "...always selects
the localhost over other servers on the same network segment, regardless
of weighting", while sensible for a system that's trying to provide most
reliable access, may not be sensible for a system that's mobile and wants to
prefer a central instance but fall back (after logging out and unmounting,
with a fairly short timeout) to a local copy so that the mounted $HOME
path remains constant.
Is there any trick that would provide the effect I want? Or failing that,
is it a reasonable enough thing to want to hope for a new non-default option,
that if used, would cause weighting to take priority over proximity (even
localhost) for specific mount point(s)?
This message posted from opensolaris.org
