There are two types of automount maps (direct and indirect).

I believe that direct maps are the ones that need to be signaled when a map changes. We have had to use direct maps for nested filesystem mounts, but do this only on an exception basis.

See the O'Reilly book "Managing NFS and NIS" by Hal Stern.

Hope this helps

Stephen Darragh

-----Original Message----- From: Rob Windsor [SMTP:windsor@adc.com] Sent: Monday, January 15, 2001 3:45 PM To: toasters@mathworks.com Subject: Re: /home layout with many filers and NIS automount

On Mon, 15 Jan 2001 10:37:38 PST, Jeffrey Krueger wrote:

...

...

There is another thing against

...

#auto_home NIS map user1 filer2:/vol/vol1/&

design. We have a lot of development servers. So any time you add/delete/modify a single user you should go trough _all_ the NIS/automount clients and run "automount" to let automountd know that passwd map has been just updated. Am I wrong again?

...

This is correct, but I simple cron job which runs periodically on all

NIS

...

clients should make short work of this task. =)

Er? Solaris? That's one of the (few) beauties of NIS -- you don't have to go around telling everything that a map has changed.

I've never gone machine-to-machine running automount(1) to kick it in the pants just because we changed the password or auto_home map. The _worst_ is that ncsd caches something and we need to kill and restart it.

Rob++

Rob Windsor E-Mail - mailto:rob_windsor@adc.com Senior Unix Systems Administrator Voice - phone:972-680-6919 Computer Services Fax - phone:972-680-0370 Broadband Access and Transport Group __o ADC Telecommunications _`<,_ Richardson, TX 75082 (_)/ (_)