*nix Documentation Project
·  Home
 +   man pages
·  Linux HOWTOs
·  FreeBSD Tips
·  *niX Forums

  man pages->Tru64 Unix man pages -> ypset (8)              
Title
Content
Arch
Section
 

ypset(8)

Contents


NAME    [Toc]    [Back]

       ypset - point ypbind at a particular server

SYNOPSIS    [Toc]    [Back]

       /usr/sbin/ypset [-V1  | -V2] [-d domain] [-h host] server

OPTIONS    [Toc]    [Back]

       Bind  server  for the (old) v.1 NIS protocol.  Bind server
       for the (current) v.2 NIS protocol.

              If no version is supplied, ypset, first attempts to
              set  the  domain for the (current) v.2 protocol. If
              this attempt fails, ypset, then attempts to set the
              domain  for  the  (old) v.1 protocol.  Set ypbind's
              binding on host, instead of locally. The  host  can
              be  specified  as  a  name  or  as an address.  Use
              domain, instead of the default domain.

DESCRIPTION    [Toc]    [Back]

       The ypset command tells ypbind to get Network  Information
       Service  (NIS)  map  information  for the specified domain
       from the ypserv process running on server.  If  server  is
       down,  or  isn't  running  ypserv,  this is not discovered
       until an NIS client process tries to get a binding for the
       domain.   At  this point, the binding set by ypset will be
       tested by ypbind.  If the binding is invalid, ypbind  will
       attempt to rebind for the same domain.

                                  Note

       The  ypbind  process  will  refuse  ypset  requests unless
       -ypset or -ypsetme are specified when ypbind is started.

       The ypset command is useful  for  binding  a  client  node
       which  is not on a broadcast net, or is on a broadcast net
       which isn't running an NIS server host. It also is  useful
       for  debugging NIS client applications, for instance where
       an NIS map only exists at a single NIS server host.

       In cases where several hosts on the local net are  supplying
  NIS  services, it is possible for ypbind to rebind to
       another host even while you attempt to  find  out  if  the
       ypset  operation  succeeded.  For example, you can type: %
       ypset host1 % ypwhich host2

       which can be confusing.  This is a  function  of  the  NIS
       subsystem's  attempt  to  load-balance among the available
       NIS servers, and occurs when host1  does  not  respond  to
       ypbind  because  it  is  not  running  ypserv (or is overloaded),
 and host2, running ypserv, gets the binding.

       The server indicates the NIS server to bind to, and can be
       specified  as  a  name  or  an address.  If specified as a
       name, ypset will attempt to use NIS  services  to  resolve
       the  name  to an address.  This will work only if the node
       has a current valid binding for the domain in question. In
       most cases, server should be specified as an address.

       Refer  to ypfiles(4) and ypserv(8) for an overview of NIS.


SEE ALSO    [Toc]    [Back]

      
      
       Commands: ypwhich(1), ypserv(8)

       Files: ypfiles(4)



                                                         ypset(8)
[ Back ]
 Similar pages
Name OS Title
ypset IRIX point ypbind at a particular NIS server
ypset FreeBSD tell ypbind(8) which YP server process to use
ypset Linux bind ypbind to a particular NIS server
ypset OpenBSD tell ypbind(8) which YP server process to use
pppoesd.conf HP-UX PPPoE (Point to Point Protocol over Ethernet) server configuration file
pppoesd HP-UX PPPoE (Point-to-Point Protocol over Ethernet) server daemon
pppoerd.conf HP-UX PPPoE (Point to Point Protocol over Ethernet) relay configuration file
pppoec.conf HP-UX PPPoE (Point to Point Protocol over Ethernet) client configuration file
sppp FreeBSD point to point protocol network layer for synchronous lines
sppp OpenBSD point to point protocol network layer for synchronous lines
Copyright © 2004-2005 DeniX Solutions SRL
newsletter delivery service