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

  man pages->IRIX man pages -> ypset (1)              
Title
Content
Arch
Section
 

Contents


ypset(1M)							     ypset(1M)


NAME    [Toc]    [Back]

     ypset - point ypbind at a particular NIS server

SYNOPSIS    [Toc]    [Back]

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

DESCRIPTION    [Toc]    [Back]

     ypset tells ypbind(1M) to get the network information service (NIS) 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 attempts to rebind	for the	same domain.

     By	default, ypbind	does not allow ypset operations	from local or remote
     hosts.  ypset returns the error message

	  ypset: Sorry,	I couldn't send	my RPC message to ypbind on host nisserver

     when ypbind rejects the attempt.

     ypset is useful for binding a client node that is not on a	broadcast net
     or	is on a	broadcast net that 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.  That is, you can
     type ypset	host1; ypwhich and get the response host2, which can be
     confusing.	 This is a function of the NIS subsystem's attempt to loadbalance
 among the available NIS servers It	occurs when host1 does not
     respond to	ypbind because it is not running ypserv	(or is overloaded) and
     host2, running ypserv, gets the binding.

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

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

OPTIONS    [Toc]    [Back]

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

     -V2	 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, attempts	to set the domain for the (old)	v.1
		 protocol.



									Page 1






ypset(1M)							     ypset(1M)



     -h	host	 Set ypbind's binding on host, instead of locally.  host can
		 be specified as a name	or as an Internet address.

     -d	domain	 Use domain instead of the default domain.

SEE ALSO    [Toc]    [Back]

      
      
     ypserv(1M), ypwhich(1), ypfiles(4).


									PPPPaaaaggggeeee 2222
[ Back ]
 Similar pages
Name OS Title
ypset Tru64 point ypbind at a particular 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