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

  man pages->HP-UX 11i man pages -> ypset (1m)              
Title
Content
Arch
Section
 

Contents


 ypset(1M)                                                         ypset(1M)




 NAME    [Toc]    [Back]
      ypset - bind to particular Network Information Service server

 SYNOPSIS    [Toc]    [Back]
      /usr/sbin/ypset [-V1] [-h host] [-d domain] server

    Remarks    [Toc]    [Back]
      The Network Information Service (NIS) was formerly known as Yellow
      Pages (yp).  Although the name has changed, the functionality of the
      service remains the same.

 DESCRIPTION    [Toc]    [Back]
      ypset tells ypbind to get Network Information Service (NIS) services
      for the specified domain from the ypserv process running on server
      (see ypserv(1M) and ypbind(1M)).  server is the NIS server that the
      NIS client binds to, and is specified as either a host name or an IP
      address.  If server is down or is not running ypserv, this is not
      discovered until a local NIS client process tries to obtain a binding
      for the domain.  The ypbind daemon then tests the binding set by
      ypset.  If the binding cannot be made to the requested server, ypbind
      attempts to rebind to another server in the same domain.

      The ypset command is useful for binding a client node that is not on a
      broadcast network, since broadcasting is the method by which ypbind
      locates a NIS server.  If a client node exists on a broadcast network
      which has no NIS server running, and if there is a network with one
      running that is available via a gateway, ypset can establish a binding
      through that gateway.  It is also useful for debugging NIS client
      applications such as when a NIS map exists only at a single NIS
      server.

      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, typing ypset host1 followed by ypwhich and receiving the
      reply host2 may be confusing.  It could occur when host1 does not
      respond to ypbind because its ypserv process is not running or is
      overloaded, and host2, running ypserv, gets the binding.

      Refer to ypfiles(4) and ypserv(1M) for an overview of the Network
      Information Service.

    Options    [Toc]    [Back]
      ypset recognizes the following options and command-line arguments:

           -V1            Bind server for the (old) Version 1 NIS protocol.

           -h host        Set the binding on host instead of locally.  host
                          can be specified as a host name or an IP address.





 Hewlett-Packard Company            - 1 -   HP-UX 11i Version 2: August 2003






 ypset(1M)                                                         ypset(1M)




           -d domain      Use domain instead of the default domain returned
                          by domainname (see domainname(1)).

 DIAGNOTICS    [Toc]    [Back]
      Sorry, ypbind on host 'name' has rejected your request.
           The user is not root, or ypbind was run without the -ypset flags.
           See ypserv(1M) for explanations of the -ypset flags.

      Sorry, I couldn't send my rpc message to ypbind on host 'name'.
           The user is not root, or ypbind was run without one of the -ypset
           flags.  See ypserv(1M) for explanations of the -ypset flags.

 WARNINGS    [Toc]    [Back]
      The server is the NIS server to bind to, specified as either a host
      name or an IP address.  If server is a host name, ypset uses the NIS
      services' hosts database (built from /etc/hosts on the master server)
      to resolve the name to an IP address.  This process works only if the
      node currently has a valid binding for the domain in question.  In
      most cases, server should be specified as an IP address.

 AUTHOR    [Toc]    [Back]
      ypset was developed by Sun Microsystems, Inc.

 SEE ALSO    [Toc]    [Back]
      domainname(1), ypwhich(1), ypserv(1M), ypfiles(4).


 Hewlett-Packard Company            - 2 -   HP-UX 11i Version 2: August 2003
[ Back ]
      
      
 Similar pages
Name OS Title
ypserv Tru64 Network Information Service (NIS) server and binder processes
ypbind Tru64 Network Information Service (NIS) server and binder processes
ypbind HP-UX Network Information Service (NIS) server, binder, and transfer processes
ypxfrd HP-UX Network Information Service (NIS) server, binder, and transfer processes
ypserv HP-UX Network Information Service (NIS) server, binder, and transfer processes
ypxfr Tru64 Transfer a Network Information Service (NIS) map from a NIS server to the local host
rpc.yppasswdd Tru64 server daemon for modifying the Network Information Service (NIS) password file
yppasswdd Tru64 server daemon for modifying the Network Information Service (NIS) password file
yppoll Tru64 determine which version of a Network Information Service (NIS) map is at a master NIS server host
bind_manual_setup Tru64 Describes how to manually set up the Berkeley Internet Name Domain (BIND) service on your network.
Copyright © 2004-2005 DeniX Solutions SRL
newsletter delivery service