On Tue, 23 Feb 1999, Alvin Oga wrote:
> client# cat /etc/auto.master
> /.autofs /etc/auto.data --timeout 60
>
> client# cat /etc/auto.data
> #
> Data -fstype=nfs machine:/usr1/data
>
> client# cd / ; ln -s .autofs/Data Data
the problem with this method is the clients all have to be modified to
utilize this scheme. it's not an out of the box solution. This may not
seem to be a problem to some people, but it is if you get a couple hundred
boxes or a bunch of engineers who constantly reinstall their systems. The
direct mount map can be put in the NIS master auto.master file indicate
the other maps and no additional work need be done on the client side. I'm
not necessarily advocating doing less work, just that it makes life less
complex for those you support if you can just hand them a box or have them
reinstall their own system without a bunch of rules and regs before it'll
run.
When I last set up a bunch of NIS/autofs systems on the network I wanted
the clients to be as generic as possible, this was a lab environment and
it was important that they be easily reinstalled without a bunch of local
hacks - I had to set up two scenarios depending on what OS you were
running - solaris or linux. for solaris I set up /usr/dist, and for linux
I had to set up /import/dist (among other mounts related to function).
This was a workable solution in our environment because there wasn't
anything before I set it up, and the solaris systems could use the /import
scenario, also. But it was still two different set-ups that were operating
system dependant. and therefore more confusion for the end-user.
cheers!
