From: Admins home (admins@vahanatech.com)
Date: Wed Nov 12 2003 - 13:37:17 EST
Hi Gurus,
I had got only one reply to my post so far - Darren Dunham thank you for
your suggestion but it did not work for me.
Darren suggested that I make sure I not only shared /usr1/share/init
read-only but also mounted it through auto.share read-only by specifying
init -o ro /usr1/share/&
in auto.share. This seemed to be a good suggestion. I tried it, but I got a
# cd /share/init
/share/init: No such file or directory.
Nov 12 09:18:25 NIS1 automountd[1118]: parse_nfs: bad entry in map
auto_share "ro"
Nov 12 09:18:25 NIS1 automountd[1118]: parse_entry: mapentry parse error:
map=auto_share key=init
Nov 12 09:18:25 NIS1 automountd[1118]: parse_nfs: bad entry in map
auto_share "ro"
Nov 12 09:18:25 NIS1 automountd[1118]: parse_entry: mapentry parse error:
map=auto_share key=init
Still trying...but any further ideas would be appreciated.
--bma
> I have configured an NIS master/slave set up for our environment NIS1 is
> the master and NIS2 is the slave server. NIS1 has a shared directory
> that will be automounted by the clients of the network. In order to
> configure failover mechanism of automount, I have put in place an NIS
> map file auto.share which contains
>
> init NIS1,NIS2:/usr1/share/&
>
> I have then replicated the NIS1:/usr1/share/init directory onto NIS2
> server using rsync and shared it accross the network using share
> command. I have read that automount failover works only for read only
> file systems. So I have shared the /usr1/share/init directoriies on both
> NIS1 and NIS2 as read-only using the -o ro option
>
> share -F nfs -o ro /usr1/share/init
>
> After having done all this, everything worked perfectly as long as both
> servers were up and running. To test the fail-over, I shutdown NIS1
> while all clients were active and the unexpected (or was it the
> expected) happened:
>
> -all commands on all clients hang ( I guess, the /share/init directory
> is in the front of /usr/bin/ /bin in the PATH environment variable)
> -users not able to login to the environment because the environment
> called from /share/init is not set. ( it gives a prompt after timing out
> on NFS) - cannot cd the /share/init it says NFS timed out waiting for
> NIS1 - it llooks like the NIS failover mechanism worked fine because on
> booting NIS1 again, ypwhich now points to NIS2 on all clients
>
> So it looks to me that all my woes are centered around the automount
> fail-over mechanism. Did I miss something? Or is it that automount just
> doesn;t failover automatically and I have to do something manually to
> set it right. I tried to login through the console of a client and ran
> the automount with no luck. Any help/pointers will be appreciated and
> will summarize. Thanks in advance.
>
> --bma
> _______________________________________________
> sunmanagers mailing list
> sunmanagers@sunmanagers.org
> http://www.sunmanagers.org/mailman/listinfo/sunmanagers
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:27:27 EDT