NIS server - Revision history

Boiarino at 20:59, 9 December 2008

2008-12-09T20:59:03Z

← Older revision		Revision as of 16:59, 9 December 2008
Line 41:		Line 41:
	10. Before starting the ypserv daemon on the slave server, stop the client with the command:		10. Before starting the ypserv daemon on the slave server, stop the client with the command:

	svcadm disable svc:/network/nis/client:default		DO NOT DO IT !!! svcadm disable svc:/network/nis/client:default

	11. When the NIS server is started, it also starts the ypbind client daemon.		11. When the NIS server is started, it also starts the ypbind client daemon.

Boiarino at 20:56, 9 December 2008

2008-12-09T20:56:47Z

← Older revision		Revision as of 16:56, 9 December 2008
Line 26:		Line 26:
	If it is not running, contact Computer Center.		If it is not running, contact Computer Center.

	8. Return to the proposed NIS slave system, and ~~enter the ypstart command to~~ start the ypbind daemon.		8. Return to the proposed NIS slave system, and start the ypbind daemon:
	svcadm enable svc:/network/nis/client:default		svcadm enable svc:/network/nis/client:default

Line 32:		Line 32:
	ypinit -s master		ypinit -s master

	where master is the name of the NIS master.		where master is the name of the NIS master (ccs10 in our case).

	Note: If you did not add the name of the NIS slave server when you initially configured		Note: If you did not add the name of the NIS slave server when you initially configured

Boiarino at 20:53, 9 December 2008

2008-12-09T20:53:03Z

← Older revision		Revision as of 16:53, 9 December 2008
Line 18:		Line 18:
	ypinit -c		ypinit -c

	5. When the system prompts for a list of NIS servers, enter the NIS master host followed by the name of the local host and all other NIS slave servers on the local network. On 'clon00' it will be ''~~clon00~~'' and ''ccs10'', on 'clon10' it will be ''clon00'' and ''ccs10''.		5. When the system prompts for a list of NIS servers, enter the NIS master host followed by the name of the local host and all other NIS slave servers on the local network. On 'clon00' it will be ''clon10'' and ''ccs10'', on 'clon10' it will be ''clon00'' and ''ccs10''.

	??? 6. Copy the /etc/nsswitch.nis file to the /etc/nsswitch.conf file. If necessary, modify the file.		??? 6. Copy the /etc/nsswitch.nis file to the /etc/nsswitch.conf file. If necessary, modify the file.

Boiarino at 15:24, 22 November 2007

2007-11-22T15:24:02Z

← Older revision		Revision as of 11:24, 22 November 2007
Line 20:		Line 20:
	5. When the system prompts for a list of NIS servers, enter the NIS master host followed by the name of the local host and all other NIS slave servers on the local network. On 'clon00' it will be ''clon00'' and ''ccs10'', on 'clon10' it will be ''clon00'' and ''ccs10''.		5. When the system prompts for a list of NIS servers, enter the NIS master host followed by the name of the local host and all other NIS slave servers on the local network. On 'clon00' it will be ''clon00'' and ''ccs10'', on 'clon10' it will be ''clon00'' and ''ccs10''.

	6. Copy the /etc/nsswitch.nis file to the /etc/nsswitch.conf file. If necessary, modify the file.		??? 6. Copy the /etc/nsswitch.nis file to the /etc/nsswitch.conf file. If necessary, modify the file.

	~~7. On the NIS master, ensure that the ypserv process is running by performing the command:~~

			??? 7. On the NIS master, ensure that the ypserv process is running by performing the command (ask Computer Center to check 'ccs10' if necessary):
	pgrep -fl ypserv		pgrep -fl ypserv
			If it is not running, contact Computer Center.
	If it is not running, ~~refer to the previous section on how to start NIS daemons on the master~~.

	8. Return to the proposed NIS slave system, and enter the ypstart command to start the ypbind daemon.		8. Return to the proposed NIS slave system, and enter the ypstart command to start the ypbind daemon.
			svcadm enable svc:/network/nis/client:default
	svcadm enable svc:/network/nis/client:default

	9. Initialize the system as an NIS slave by performing the command:		9. Initialize the system as an NIS slave by performing the command:
			ypinit -s master
	ypinit -s master

	where master is the name of the NIS master.		where master is the name of the NIS master.

Boiarino at 15:18, 22 November 2007

2007-11-22T15:18:21Z

← Older revision		Revision as of 11:18, 22 November 2007
Line 18:		Line 18:
	ypinit -c		ypinit -c

	5. When the system prompts for a list of NIS servers, enter the NIS master host followed by the name of the local host and all other NIS slave servers on the local network.		5. When the system prompts for a list of NIS servers, enter the NIS master host followed by the name of the local host and all other NIS slave servers on the local network. On 'clon00' it will be ''clon00'' and ''ccs10'', on 'clon10' it will be ''clon00'' and ''ccs10''.

	6. Copy the /etc/nsswitch.nis file to the /etc/nsswitch.conf file. If necessary, modify the file.		6. Copy the /etc/nsswitch.nis file to the /etc/nsswitch.conf file. If necessary, modify the file.

Boiarino at 15:13, 22 November 2007

2007-11-22T15:13:25Z

← Older revision		Revision as of 11:13, 22 November 2007
Line 10:		Line 10:
	#		#

	~~DONE ???~~ 2. ~~Execute~~ the ~~domainname command to set~~ the ~~local NIS~~ domain.		2. Create or populate the ''/etc/defaultdomain'' file with the domain name. For clon machines ''/etc/defaultdomain'' should contains ''CCCHP''.
	~~# domainname domainname~~
	For ~~example:~~
	~~# domainname classroom~~.~~Central.Sun.COM~~

	~~DONE ???~~ 3. ~~Create or populate~~ the ~~/etc/defaultdomain file with~~ the domain ~~name~~.		3. Execute the domainname command to set the local NIS domain. For clon machines:
			domainname CCCHP

	~~DONE ???~~ 4. Initialize the system as an NIS client by performing the command:		4. Initialize the system as an NIS client by performing the command:
	# ypinit -c		ypinit -c

	~~DONE ???~~ 5. When the system prompts for a list of NIS servers, enter the NIS master host followed by the name of the local host and all other NIS slave servers on the local network.		5. When the system prompts for a list of NIS servers, enter the NIS master host followed by the name of the local host and all other NIS slave servers on the local network.

	6. Copy the /etc/nsswitch.nis file to the /etc/nsswitch.conf file. If necessary, modify the file.		6. Copy the /etc/nsswitch.nis file to the /etc/nsswitch.conf file. If necessary, modify the file.

Boiarino at 19:52, 1 September 2007

2007-09-01T19:52:48Z

← Older revision		Revision as of 15:52, 1 September 2007
Line 10:		Line 10:
	#		#

	2. Execute the domainname command to set the local NIS domain.		DONE ??? 2. Execute the domainname command to set the local NIS domain.

	# domainname domainname		# domainname domainname

	For example:		For example:

	# domainname classroom.Central.Sun.COM		# domainname classroom.Central.Sun.COM

	3. Create or populate the /etc/defaultdomain file with the domain name.		DONE ??? 3. Create or populate the /etc/defaultdomain file with the domain name.
	~~4. Initialize the system as an NIS client by performing the command:~~

			DONE ??? 4. Initialize the system as an NIS client by performing the command:
	# ypinit -c		# ypinit -c

	5. When the system prompts for a list of NIS servers, enter the NIS master host followed by the name of the local host and all other NIS slave servers on the local network.		DONE ??? 5. When the system prompts for a list of NIS servers, enter the NIS master host followed by the name of the local host and all other NIS slave servers on the local network.
	6. Copy the /etc/nsswitch.nis file to the /etc/nsswitch.conf file. If necessary, modify the file.
	7. On the NIS master, ensure that the ypserv process is running by performing the command:		6. Copy the /etc/nsswitch.nis file to the /etc/nsswitch.conf file. If necessary, modify the file.

			7. On the NIS master, ensure that the ypserv process is running by performing the command:

			pgrep -fl ypserv

	~~# pgrep -fl ypserv~~		If it is not running, refer to the previous section on how to start NIS daemons on the master.

	~~If it is not running~~, ~~refer to~~ the ~~previous section on how~~ to start ~~NIS daemons on~~ the ~~master~~.		8. Return to the proposed NIS slave system, and enter the ypstart command to start the ypbind daemon.

	~~8. Return to the proposed NIS slave system, and enter the ypstart command to start the ypbind daemon.~~		svcadm enable svc:/network/nis/client:default

	~~# svcadm enable svc~~:~~/network/nis/client:default~~		9. Initialize the system as an NIS slave by performing the command:

	~~9. Initialize the system as an NIS slave by performing the command:~~		ypinit -s master

	~~# ypinit -s~~ master		where master is the name of the NIS master.

	~~where~~ master is the ~~name~~ of the NIS master.		Note: If you did not add the name of the NIS slave server when you initially configured
			the NIS master server using the ypinit command,enter the ypinit -m command once more on
			the NIS master server. In the process of updating the NIS master, the script prompts you
			for confirmation when it is about to destroy the existing domain database. Confirm by entering y.

	Note: If you did not add the name of the NIS slave server when you initially configured the NIS master server using the ypinit command, enter the ypinit -m command once more on the NIS master server. In the process of updating the NIS master, the script prompts you for confirmation when it is about to destroy the existing domain database. Confirm by entering y.		10. Before starting the ypserv daemon on the slave server, stop the client with the command:
	10. Before starting the ypserv daemon on the slave server, stop the client with the command:

	# svcadm disable svc:/network/nis/client:default		svcadm disable svc:/network/nis/client:default

	11. When the NIS server is started, it also starts the ypbind client daemon.		11. When the NIS server is started, it also starts the ypbind client daemon.

	# svcadm enable svc:/network/nis/server:default		svcadm enable svc:/network/nis/server:default

	12. To test NIS client functionality on the newly configured NIS slave server, perform the command:		12. To test NIS client functionality on the newly configured NIS slave server, perform the command:

	# ypwhich -m		ypwhich -m

	The output shows a list of maps together with the NIS master server for each map.		The output shows a list of maps together with the NIS master server for each map.

Boiarino at 19:49, 1 September 2007

2007-09-01T19:49:28Z

← Older revision		Revision as of 15:49, 1 September 2007
Line 6:		Line 6:
	# NIS servers		# NIS servers
	#		#
	129.57.167.14 clon10.jlab.org clon10		129.57.167.14 clon10.jlab.org clon10
	129.57.33.22 ccs10.jlab.org ccs10		129.57.33.22 ccs10.jlab.org ccs10
	#		#

Boiarino at 19:49, 1 September 2007

2007-09-01T19:49:02Z

← Older revision		Revision as of 15:49, 1 September 2007
Line 1:		Line 1:
	CLON cluster has NIS slave servers to provide backup if the NIS master server becomes unavailable. To configure an NIS slave server, complete the following steps on the system that you want to designate as the slave server:		CLON cluster has NIS slave servers to provide backup if the NIS master server becomes unavailable. To configure an NIS slave server, complete the following steps on the system that you want to designate as the slave server:

	1. Edit the /etc~~/inet~~/hosts file to ensure that the NIS master and all NIS slave servers have been defined.		1. Edit the /etc/hosts file to ensure that the NIS master and all NIS slave servers have been defined. For example on ''clon00'' two extra NIS servers must be specified:

			#
			# NIS servers
			#
			129.57.167.14 clon10.jlab.org clon10
			129.57.33.22 ccs10.jlab.org ccs10
			#

	2. Execute the domainname command to set the local NIS domain.		2. Execute the domainname command to set the local NIS domain.

Boiarino at 19:47, 1 September 2007

2007-09-01T19:47:16Z

← Older revision		Revision as of 15:47, 1 September 2007
Line 1:		Line 1:
	CLON cluster has NIS slave servers to provide backup if the NIS master server becomes unavailable. To configure an NIS slave server, complete the following steps on the system that you want to designate as the slave server:		CLON cluster has NIS slave servers to provide backup if the NIS master server becomes unavailable. To configure an NIS slave server, complete the following steps on the system that you want to designate as the slave server:

	1. Edit the /etc/inet/hosts file to ensure that the NIS master and all NIS slave servers have been defined.		1. Edit the /etc/inet/hosts file to ensure that the NIS master and all NIS slave servers have been defined.

	2. Execute the domainname command to set the local NIS domain.		2. Execute the domainname command to set the local NIS domain.