Re: NIS server selection

From: Dan Nelson (dnelson_at_allantgroup.com)
Date: 07/08/04

  • Next message: Beecher Rintoul: "Fatal Server error" 
    Date: Thu, 8 Jul 2004 15:44:18 -0500
To: Doug Hardie <bc979@lafn.org>

    In the last episode (Jul 08), Doug Hardie said:
    > I have NIS running on a few servers. I have had them configured with
    > the -S option with only their host name so they would use the local
    > resolver. However, after a few problems with ypserv dying I tried
    > adding additional servers to the -S list. Everything was as normal
    > till I killed ypserv on the local machine. Then it switched to the
    > first host listed after the local name in the -S list. Access to NIS
    > records worked fine.
    >
    > Then I tried to revert back to the local server. Restarting ypserv
    > had no effect. NIS requests were still sent to the other server. I
    > killed ypbind and restarted it with the full list. All requests were
    > still sent to the other server. I killed ypbind again and restarted
    > it with just the local server in the -S list. The request then were
    > split about half and half with the local server and other server.
    > How does ypbind know about the other server anymore?

    Running processes will talk to the server they originally made a
    connection to, until that connection fails. Only then will they
    contact their local ypbind and ask for another server. ypbind is not
    contacted on every lookup.
     
    > I had to kill ypserv on the other server, wait for some requests to
    > timeout (ypbind is a persistent bugger) and then it switched. Surely
    > there has to be an easier way to do this. I am trying to have ypbind
    > use the local server if its working and otherwise one of the other
    > servers. If the local ypbind gets restarted i would like it to revert
    > back to using it.

    The best you can do is make sure "ypwhich" points to the local machine
    so that subsequent processes will use it. You can't force existing
    processes to switch. 

    -- 
	Dan Nelson
	dnelson@allantgroup.com
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
  • Next message: Beecher Rintoul: "Fatal Server error"

    Relevant Pages

    • Re: Conditionally disabling ypbind
      ... I figured out that ypbind was set to use broadcast to resolve NIS ... I've added explicit server entries to /etc/yp.conf for ... The problem is that there is no NIS server at home, and during boot ...
      (Fedora)
    • Re: Solaris NIS server and Linux NIS client : problems
      ... > hosts: nis dns files ... Can't bind to server which serves ... Maybe try starting up ypbind manually with the debug switch, ... Juhan Leemet ...
      (comp.os.linux.networking)
    • Re: Solaris NIS server and Linux NIS client : problems
      ... > hosts: nis dns files ... Can't bind to server which serves ... Maybe try starting up ypbind manually with the debug switch, ... Juhan Leemet ...
      (comp.unix.solaris)
    • Re: NIS client couldnt log in
      ... >> off iptables, the client bound to the server and all the yptools ... and ypbind in broadcast mode (ypcat and ypwhich would ... >> work at all if i specified the server). ... Further, ypbind uses the ...
      (RedHat)
    • Re: Having problems with NIS and SAM I am.
      ... When I tried to start NIS from the init script, ... I can't set up a udp connection to ypbind on host ducati ... > NIS does not work properly if the server has two IP-addresses in the ... > same subnet, and it does not work properly, if there are two connections ...
      (comp.sys.hp.hpux)