Switch to SpeakEasy.net DSL

The Modular Manual Browser

Home Page
Manual: (HP-UX-11.11)
Apropos / Subsearch:
optional field

 rpc.nisd(1M)							rpc.nisd(1M)

      rpc.nisd, rpc.nisd_resolv, nisd, nisd_resolv - NIS+ service daemon

      /usr/sbin/rpc.nisd [ -ACDFhlv ] [ -Y [ -B [ -t netid ]]]
	   [ -d dictionary ] [ -L load ] [ -S level ]


      The rpc.nisd daemon is an RPC service that implements the NIS+
      service.	This daemon must be running on all machines that serve a
      portion of the NIS+ namespace.

      rpc.nisd is usually started from a system startup script.

      rpc.nisd_resolv is an auxillary process that is started by rpc.nisd
      when it is invoked with -B option.  Note that rpc.nisd_resolv should
      not be started independently.

      -A	Authentication verbose mode.  The daemon logs all the
		authentication related activities to syslogd(1M) with
		LOG_INFO priority.

      -B	Provide ypserv compatible DNS forwarding for NIS host
		requests.  The DNS resolving process, rpc.nisd_resolv, is
		started and controlled by rpc.nisd.  This option requires
		that the /etc/resolv.conf file be set up for communication
		with a DNS nameserver.	The nslookup utility can be used to
		verify communication with a DNS nameserver.  See resolver(4)
		and nslookup(1).

      -C	Open diagnostic channel on /dev/console.

      -D	Debug mode (don't fork).

      -F	Force the server to do a checkpoint of the database when it
		starts up.  Forced checkpoints may be required when the
		server is low on disk space.  This option removes updates
		from the transaction log that have propagated to all of the

      -L number Specify the ``load'' the NIS+ service is allowed to place on
		the server.  The load is specified in terms of the number of
		child processes that the server may spawn.  This number must
		be at least 1 for the callback functions to work correctly.
		The default is 128.

      -S level	Set the authorization security level of the service.  The
		argument is a number between 0 and 2.  By default, the

 Hewlett-Packard Company	    - 1 -   HP-UX Release 11i: November 2000

 rpc.nisd(1M)							rpc.nisd(1M)

		daemon runs at security level 2.

		0    Security level 0 is designed to be used for testing and
		     initial setup of the NIS+ namespace.  When running at
		     level 0, the daemon does not enforce any access
		     controls.	Any client is allowed to perform any
		     operation, including updates and deletions.

		1    At security level 1, the daemon accepts both AUTH_SYS
		     and AUTH_DES credentials for authenticating clients and
		     authorizing them to perform NIS+ operations.  This is
		     not a secure mode of operation since AUTH_SYS
		     credentials are easily forged.   It should not be used
		     on networks in which any untrusted users may
		     potentially have access.

		2    At security level 2, the daemon accepts only AUTH_DES
		     credentials for authentication and authorization.	This
		     is the highest level of security currently provided by
		     the NIS+ service.	This is the default security level
		     if the -S option is not used.

      -Y	Put the server into NIS (YP) compatibility mode.  When
		operating in this mode, the NIS+ server will respond to NIS
		Version 2 requests using the version 2 protocol.  Because
		the YP protocol is not authenticated, only those items that
		have read access to nobody (the unauthenticated request)
		will be visible through the V2 protocol. It supports only
		the standard Version 2 maps in this mode (see -B option and
		NOTES in ypfiles(4)).

      -d dictionary
		Specify an alternate dictionary for the NIS+ database.	The
		primary use of this option is for testing.  Note that the
		string is not interpreted, rather it is simply passed to the
		db_initialize function.	 See nis_db(3N).

      -h	Print list of options.

      -t netid	Use netid as the transport for communication between
		rpc.nisd and rpc.nisd_resolv.  The default transport is tcp.

      -v	Verbose.  With this option, the daemon sends a running
		narration of what it is doing to the syslog daemon (see
		syslogd(1M)) at LOG_INFO priority.  This option is most
		useful for debugging problems with the service (see also -A

      The following example sets up the NIS+ service.

 Hewlett-Packard Company	    - 2 -   HP-UX Release 11i: November 2000

 rpc.nisd(1M)							rpc.nisd(1M)


      The following example sets up the NIS+ service, emulating YP with DNS

	   rpc.nisd -YB

    Environment Variables
      NETPATH	     The transports that the NIS+ service will use can be
		     limited by setting this environment variable (see

	   /var/nis/parent.object   This file contains an XDR encoded NIS+
				    object that describes the namespace
				    above a root server.  This parent
				    namespace may be another NIS+ namespace
				    or a foreign namespace such as one
				    served by the Domain Name Service.	It
				    is only present on servers that are
				    serving the root of the namespace.
	   /var/nis/root.object	    This file contains an XDR encoded NIS+
				    object that describes the root of the
				    namespace.	It is only present on
				    servers that are serving the root of the
				    initialization script for NIS+

      rpc.nisd and rpc.nisd_resolv were developed by Sun Microsystems, Inc.

      nis_cachemgr(1M), nisinit(1M), nissetup(1M), nslookup(1), syslogd(1M),
      nis_db(3N), netconfig(4), nisfiles(4), resolver(4), ypfiles(4).

 Hewlett-Packard Company	    - 3 -   HP-UX Release 11i: November 2000