On Tue, 16 Jan 2001 18:16:10 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.
As noted later in this thread, I stand corrected. What I left out is the fact that only indirect mount maps require kicking the automounter. Direct mount maps aren't affected.
Uh, I hate to beat the subject to death, but you have that backwards.
Only direct mount maps require automount(1)-type frobbing to wake up.
Indirect maps update automagically since automountd already has complete control of the mountpoint.
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 (_)/ (_)