Planning an automount configuration
In a larger network (10 or more workstations), it may be desirable
to ``distribute'' automount functionality using
NIS (Network Information Service), particularly if you need:
If you wish to distribute automount functionality, you
must create automount maps on the NIS master
``Managing automount with NIS''.
Any further automount administration is performed on
the NIS master server.
distributed home directories; this allows users to log in and
use their home environment from any machine in an NIS domain
redundant read-only filesystem access; this allows clients to
mount the desired filesystem from the first server to respond
NIS-distributed automount maps can be modified on a
per-client basis with local automount maps; for more
``Creating local automount maps''.
However, NIS management may not be justified if many clients
have extensive local automount maps.
In smaller installations, where NIS management is unnecessary,
it may be desirable to use automount when workstations
double as NFS servers and clients. To optimize performance
and user access, we recommend that you:
identify all NFS-exported directories on your network and
ascertain the frequency of use for each.
if necessary, move directories to other servers to balance the
remote mount load.
decide which directories should be conventionally mounted and
which automounted; record the decision in your system log.
modify /etc/default/filesys to add conventional mounts
and create automount maps for automounts; after backing up
existing configuration files, transfer these files to other
machines on the network.
Creating master automount maps
© 2003 Caldera International, Inc. All rights reserved.
SCO OpenServer Release 5.0.7 -- 11 February 2003