Network Information Service (NIS) B.11.31.
© Copyright 2008 Hewlett-Packard Development Company, L.P Legal Notices © Copyright 2008 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license.
Table of Contents About This Document.....................................................................................................................9 Intended Audience...............................................................................................................9 Document Organization.......................................................................................................9 Typographic Conventions............................................................................
Verifying the Contents of an NIS Map...............................................................................35 Modifying an NIS Map.......................................................................................................35 Adding an AutoFS Map to the NIS Domain......................................................................36 Removing an AutoFS Map from the NIS Domain.............................................................37 Adding a Slave Server to the NIS Domain............
B NIS Configuration File /etc/rc.config.d/namesvrs........................................................................71 C Using NIS in Compat Mode......................................................................................................73 Using Netgroups in the /etc/passwd File......................................................................73 Editing the Slave Server's passwd File in Compat Mode...................................................
List of Figures 1-1 1-2 1-3 6 Illustration of a Sample NIS Network.........................................................................12 Flow of Information in an NIS Domain......................................................................17 Servers Serving Multiple NIS Domains......................................................................
List of Tables 1-1 1-2 1-3 NIS Daemons...............................................................................................................14 NIS Commands...........................................................................................................14 NIS Source Files...........................................................................................................
List of Examples 4-1 4-2 5-1 5-2 8 Allowing a Specific Client to Access the Slave Server................................................50 Allowing Selected Clients on the same Subnet to Access the Slave Server................50 Configuring Safe Servers for an NIS Client................................................................56 Configuring Safe Servers From a Subnet for an NIS Client........................................
About This Document This document describes how to configure and administer Network Information Service (NIS™) on HP-UX 11i v3 systems. It also describes how to troubleshoot NIS. Intended Audience This document is intended for system administrators who install and configure UNIX® systems along with the Open Network Computing (ONC) suite of products.
monospace italic % $ # \ [ ] | Ctrl+A Computer output, files, directories, software elements such as command options, function names, and parameters, for example, Read tunables from the /etc/vx/tunefstab file. New terms, book titles, emphasis, and variables replaced with a name or value. C shell prompt Bourne/Korn shell prompt Superuser prompt (all shells) Continued input on the following line; do not type this character. In command synopsis, brackets indicate an optional argument. For example, ls [ -a ].
1 Introduction This chapter describes the Network Information Service (NIS) and its features. It also discusses the components in an NIS network.
NIS Slave Server An NIS slave server service requests from an NIS client. Configuring one or more NIS slave servers, to service client requests reduces the load from the NIS master server. The NIS maps are created on the NIS master server and transferred to the slave servers. Changes to the NIS maps must be made on the NIS master server, which then transfers the updated copies of the maps to the NIS slave servers.
5 connect to the master and slave servers to obtain NIS configuration information over the 20.21.12.0 network. The entries in the /etc/rc.config.d/namesvrs file on both the master and slave servers are shown in Figure 1-1. The daemons running on the NIS master server are rpcbind, ypserv, ypxfrd, rpc.yppasswdd, rpc.ypupdated, keyserv, and ypbind. The daemons running on the NIS slave server are rpcbind, ypserv, ypxfrd, keyserv, and ypbind. The ypbind and rpcbind daemons run on the NIS client.
Table 1-1 NIS Daemons NIS Daemon Description ypxfrd Copies the NIS maps to the local host from an NIS server. This daemon runs on any NIS master and slave server. ypserv Maintains the NIS database of maps, and services the NIS client requests. This daemon runs on any NIS master and slave server. ypbind Maintains binding information for the hosts. This daemon runs on any NIS client. yppasswdd Changes the password associated with a given login name. This daemon runs only on the NIS master server.
Table 1-2 NIS Commands (continued) Command Description yppasswd Changes a login password that is stored in the NIS passwd map. The password stored in the NIS passwd map may be different from the one stored on your local system. For more information, see yppasswd (1). yppoll Returns the name of the master server for an NIS map and the time at which the map was built. It also specifies the domain to which the map belongs. For more information, see yppoll (1M).
Table 1-3 NIS Source Files (continued) NIS Source File Description /etc/group A list of group names, along with encrypted password and numerical group ID. See group (4). /etc/services A file that associates network services with the port numbers and protocols, which the services use. See services (4). /etc/protocols A file that associates network protocols with protocol numbers. See protocols (4). /etc/networks A file that associates IP addresses with official network names and aliases.
Figure 1-2 Flow of Information in an NIS Domain The flow of NIS information from the master server to the client includes the following steps: 1. 2. 3. 4. The NIS maps are created on the master server. The NIS maps are propagated from the master server to the slave server. A call on the NIS client, such as gethostbyname, references the maps on the NIS servers to resolve the call. The NIS server returns the data to the NIS client. A host cannot function as the master server for more than one NIS domain.
Figure 1-3 Servers Serving Multiple NIS Domains Startup Scripts in NIS Services This section discusses the startup sequence for the NIS daemons during a normal system boot. Following are the NIS startup scripts: • • /sbin/init.d/nis.server /sbin/init.d/nis.client These scripts can be used to start and stop NIS on a system. As part of startup, they read the /etc/rc.config.d/namesvrs file to determine the daemons that must be started, and detect whether the system is a server or a client. The nis.
• • Starts the ypserv daemon if it is not already running on both the master and the slave servers. Starts ypxfrd if it is not already running on both the master and the slave servers. The nis.client script is executed at run level 2 on the systems configured as NIS client. This script performs the following tasks: • • • • Starts the rpcbind daemon if it is not already running. Sets the domainname. Starts ypbind if it is not already running. Starts keyserv if it is not already running.
Shadow password mode enhances the password security of the system by maintaining user passwords in a different file called /etc/shadow, and replaces the encrypted password in the passwd file with x. This enhances the password security of the system. You can convert a system to shadow mode using the pwconv command , and revert the system using the pwunconv command.
and IPv6 information. Ipnodes are a superset of hosts and act as the host database for IPv6 information. NIS supports ipnodes using the /etc/nsswitch.conf file. For more information about the /etc/nsswitch.conf file, see nsswitch.conf (4). • Alternate Directory for the passwd File On HP-UX 11i v3, users may specify a directory other than the default directory (/etc), where NIS must look for the passwd file. A new option –D is introduced to support this feature on the rpc.yppasswdd server.
HP recommends that you migrate to the next version of the NIS protocol, NIS version 2 (NISv2), because NISv2 supports all the functionalities that NISv1 supports. • Files for Resolving Map Nicknames NIS supports the creation of nicknames for map. The NIS commands, ypcat and ypmatch, use the /var/yp/nicknames file to resolve the map nicknames. Following are the contents of the /var/yp/nicknames file: passwd passwd.byname group group.byname networks networks.byaddr hosts hosts.byname ipnodes ipnodes.
2 Planning an NIS Network This chapter describes how to plan the layout of your NIS network. This chapter discusses the following topics: • • • “Determining the Number of NIS Domains Required” (page 23) “Determining the Number of NIS Servers ” (page 23) “Determining the Hosts that will be NIS Servers” (page 23) Determining the Number of NIS Domains Required For many sites, all hosts can belong to the same domain and it is not necessary to set up more than one domain.
3 Configuring and Administering an NIS Master Server An NIS master server holds the source files for all the NIS maps in a domain. Any changes to the NIS maps must be made on the NIS master server. The NIS master server delivers information to the NIS clients and supplies the NIS slave servers with the latest maps. An NIS master server can also act as NIS client.
NOTE: Back up the /etc/passwd file before you perform the steps described in this section. 1. 2. 3. Log in to the NIS master server as a superuser. Create a new directory: # cd /etc # mkdir nis Copy the /etc/passwd file from each host, including the NIS master server, in your NIS domain as /etc/nis/passwd.hostname, to the host designated at the master server. where: hostname specifies the name of the host to which the file belongs.
For more information about the private passwd file, see “Configuring the NIS Master Server to Use a Private passwd File” (page 32). 10. Remove all the /etc/nis/passwd.hostname files from the NIS master server. For more information about the passwd file, see passwd (4). For more information about the sort command, see sort (1). Creating the Master group File The NIS master server group file is used to create NIS groups that store group information on the NIS server.
7. 8. 9. Merge the groups with the same name into one group to remove the duplicate entries. Sort the temporary group file by group ID: # sort -o /etc/nis/group.temp -t: -k3n,3 /etc/nis/group.temp Examine the /etc/nis/group.temp file for duplicate group IDs. NOTE: Ensure that each group has a unique group ID. 10. Move the sorted /etc/nis/group.temp file to the /etc/group file. The /etc/group file is used to generate the group map for the NIS domain. 11. Remove the /etc/nis/group.
5. # cat hosts hosts.hostname1 hosts.hostname2... > hosts.temp Sort the temporary hosts file by IP address: # sort -o /etc/nis/hosts.temp -b -k1,1 /etc/nis/hosts.temp NOTE: The NIS master server does not require that the hosts file be sorted in any particular way. However, sorting the hosts file facilitates the search for duplicate entries. 6. Examine the /etc/nis/hosts.temp file for duplicate IP addresses, and remove the duplicate entries: # sort -o /etc/nis/hosts.temp -b -k3, /etc/nis/hosts.
NOTE: Back up the /etc/rc.config.d/namesvrs file and the /etc/ nsswitch.conf file before you perform the steps described in this section. 1. 2. Log in as a superuser to the host that is designated as the master server.
8. 9. Set up a system as an NIS client: # /usr/sbin/ypinit -c Copy the /etc/nsswitch.nis file to the /etc/nsswitch.conf directory: # cp /etc/nsswitch.nis /etc/nsswitch.conf CAUTION: Any customized files may be overwritten while copying the /etc/ nsswitch.nis file in the/etc/nsswitch.conf directory. 10. Run the NIS startup scripts: # /sbin/init.d/nis.server start # /sbin/init.d/nis.client start The NIS master server now runs as both an NIS master server and an NIS client.
mail.byaddr mastername mail.aliases mastername netgroup.byhost mastername netgroup.byuser mastername netgroup mastername protocols.byname mastername protocols.bynumber mastername servi.bynp mastername services.byname mastername rpc.byname mastername rpc.bynumber mastername networks.byaddr mastername networks.byname mastername ipnodes.byaddr mastername ipnodes.byname mastername hosts.byaddr mastername hosts.byname mastername group.bygid masternamegroup.byname mastername passwd.byuid mastername passwd.
3. 4. Edit the /etc/passwd file so that pure NIS users cannot access the local system, which serves as the NIS master server. Edit the /var/yp/Makefile file. Replace: PWFILE=$(DIR)/passwd with PWFILE=$(DIR)/passwd.yp 5. In the /etc/rc.config.d/namesvrs file, modify the value of the YPPASSWDD_OPTIONS variable from: YPPASSWDD_OPTIONS=”/etc/passwd -m passwd PWFILE=/etc/passwd” to: YPPASSWDD_OPTIONS=”/etc/passwd.yp -m passwd PWFILE=/etc/passwd.yp” 6. 7.
The -D /etc/nis option must be added to the YPPASSWDD_OPTIONS variable in the /etc/rc.config.d/namesvrs file. You must restart the NIS server each time you modify the namesvrs file. IMPORTANT: Back up the /etc/rc.config.d/namesvrs file before you perform the steps described in this section. To set up an alternate directory for the password file, complete the following steps: 1. 2. 3. Log in to the NIS master server as a superuser. Stop the NIS server: #/sbin/init.d/nis.server stop Modify the /etc/rc.
Example 1 The following entry from a /var/yp/securenets file allows only the NIS client at IP address 20.21.12.13 to request information from the NIS master server: 255.255.255.255 20.21.12.13 Each bit is set in the address mask. Only the host whose IP address is 20.21.12.13 is allowed access to the master server. Example 2 The following entry from a /var/yp/securenets file allows hosts on the 20.21.12.13 network, to request NIS information or transfer NIS maps from the master server: 255.255.255.0 20.21.
2. Modify the following source files of the NIS map: • /etc/hosts • /etc/passwd • /etc/group For example, if you want to modify the NIS hosts map, modify the /etc/hosts file. 3.
passwd.byuid protocols.byname protocols.bynumber rpc.bynumber \ services.byname vhe_list publickey.byname netid.byname mail.byaddr \ mail.aliases auto.master rpc.byname servi.bynp auto.tools” 3. Modify the /var/yp/Makefile file: • Add the AutoFS map to the list of maps that begin with all:, as follows: all: passwd group hosts networks rpc services protocols \ netgroup aliases publickey netid vhe_list auto.master\ auto.tools • Duplicate the section that begins with $(YPDBDIR)/$(DOM)/auto_master.time.
3. Modify the /var/yp/Makefile: • Remove the auto.tools map from the list of maps that begin with all:. • Remove the auto_tools.time section. For example: $ (YPDBDIR)/$(DOM)/auto_tools.time: $(DIR)/auto_tools @(sed -e ”s/^[ | ]*//g” -e ”/^#/d” -e s/#.*$$// \ $(DIR)/auto_tools $(CHKPIPE)) |\ $(MAKEDBM) - $(YPDBDIR) /$(DOM)/auto.tools;\ @touch $(YPDBDIR)/$(DOM)/auto_tools.time;\ @echo ”updated auto.tools”;\ @if [ ! $(NOPUSH) ]; then $(YPPUSH) -d $(DOM) auto.
# vi /var/yp/marketing/tempfile In the vi editor window, enter the host name of the slave server. For example: ocelot 5. 6. Regenerate the ypservers map from the ASCII file: # /usr/sbin/makedbm tempfile ypservers Log in to the new slave server as a superuser, and configure it as an NIS slave server. For more information on configuring an NIS slave server, see “Configuring and Administering an NIS Slave Server” (page 45). For more information, see makedbm(1M) and ypfiles(4).
For more information, see makedbm(1M) and ypfiles(4). Enabling the DNS Forwarding Mode The Domain Name Service (DNS) forwarding mode enables the NIS server to use DNS to service hosts or ipnodes requests, whenever the requested information is not available in the NIS maps. NIS can automatically fetch the information from DNS and this operation is transparent to the user or application and can be achieved without any change to the /etc/nsswitch.conf configuration file.
Enabling the Shadow Password Mode Shadow password mode enhances the password security of the system by maintaining user passwords in a different file called /etc/shadow, and replaces the encrypted password in the passwd file with x. To enable the shadow password mode on an NIS master server, complete the following steps: 1. 2. Log in to the NIS master server as a superuser. Set the SHADOW_MODE variable to 1 in the /etc/rc.config.d/namesvrs file: SHADOW_MODE=1 3.
Create the /var/yp/ypxfr.log file to log messages: # /usr/bin/touch /var/yp/ypxfr.log Stop logging of ypxfr and to remove the ypxfr.log file: # /usr/bin/rm /var/yp/ypxfr.log The log output of the ypxfr command cannot be redirected. For more information, see ypxfr(1M), cron(1M), and yppush(1M) manpages. • Starting and Stopping the Logging of the ypserv daemon By default, the ypserv daemon logs messages to the file /var/yp/ypserv.log, if it exists. Verify whether the /var/yp/ypserv.
# /sbin/init.d/nis.client start • Configuring yppasswdd Logging To configure the yppasswdd logging, complete the following steps: 1. Stop yppasswdd: # /sbin/init.d/nis.server stop 2. Add the -l logfile option to the YPPASSWD_OPTIONS variable in the /etc/rc.config.d/namesvrs file: YPPASSWDD_OPTIONS=”-l /var/yp/nis_log” If you specify a log file with the -l option, yppasswdd shares that log file with the other NIS daemons. 3. Restart the NIS server: # /sbin/init.d/nis.
4 Configuring and Administering an NIS Slave Server This chapter describes how to configure an NIS slave server to provide system information from the NIS maps to the NIS clients in an NIS domain. In an NIS domain, you must configure at least one host as an NIS slave server to attend to NIS clients when the NIS master server is busy or unavailable.
is the numerical user ID. is the numerical group ID. is a field that contains user information; such as name, office location, address, and phone number. In the sample /etc/ passwd file, this field is empty. is the initial working directory. is the program to use as the shell prompt. 0 3 / /bin/ksh NOTE: Back up the /etc/passwd file before modifying it.
NOTE: Back up the /etc/group file before modifying it. Remove all users from the /etc/group file, except the system entries required for the system to boot and function properly. The changes made to the /etc/group file on an NIS slave server must be identical to the changes made to the /etc/group on an NIS client. Enabling the NIS Slave Server To enable the NIS slave server, complete the following steps: 1. 2. Log in to the NIS master server.
If the slave server serves a different domain from the one set by the domainname command, you must specify the domainname after NIS_server_name. 9. Set up the system as an NIS client and a NIS master server: # /usr/sbin/ypinit -c 10. Copy the /etc/nsswitch.nis file to the /etc/nsswitch.conf file: # cp /etc/nsswitch.nis /etc/nsswitch.conf CAUTION: Any customized files may be overwritten while copying the /etc/ nsswitch.nis file in the/etc/nsswitch.conf directory. 11. Start the NIS scripts: # /sbin/init.
2. From the /usr/newconfig/var/yp directory, copy any one of the sample scripts ypxfr_1perday, ypxfr_2perday, or ypxfr_1perhour to the /var/yp directory: # cp /usr/newconfig/var/yp/ypxfr_1perday /var/yp # cp /usr/newconfig/var/yp/ypxfr_2perday /var/yp # cp /usr/newconfig/var/yp/ypxfr_1perhour /var/yp These scripts contain commands to transfer a set of maps from the NIS master to the slave server at a particular frequency. 3. Create a crontab file to invoke these NIS scripts at regular intervals.
where: IP_address address_mask specifies the Internet address of an NIS client, NIS slave server, or the subnet that requests NIS information or transfers NIS maps from the NIS master server. indicates the important bit fields in the IP_address. If a bit is set in the address_mask field, the corresponding bit in the source address of any incoming NIS requests must match the same bit in the IP_address field.
5 Configuring and Administering an NIS Client An NIS client obtains its configuration information using the NIS map information from either an NIS master server or an NIS slave server. You must configure the NIS master server before configuring the NIS client.
NOTE: Back up the /etc/passwd file before modifying it. To modify the NIS client /etc/passwd file, remove all users from the /etc/passwd file, except the root user, other users with administrative privileges, and the system entries required for the system to boot and function properly. System entries have user IDs less than 100. The changes made to the /etc/passwd file on an NIS client must be identical to the changes made on an NIS slave server. For more information, see passwd (4).
NOTE: Back up the /etc/group file before modifying it. To modify the NIS client's /etc/group file, remove all groups from the /etc/group file except the entries required for the system to boot and function properly. The groups that will be required are the groups listed in the /etc/passwd file. The changes made to the /etc/group file on an NIS client must be identical to the changes made on the NIS slave server. For more information, see group (4).
# ypinit -c The system displays the following information: If it is desired that NIS client, has to bind to a particular NIS server, a list of NIS servers should be constructed. Please continue to add the names of NIS servers in the order of preference, one per line. When done with the list, type a Ctrl+D or a return on a line by itself next host to add: next host to add: The current list of yp servers looks like this: Is this correct? [y/n: y] 8.
networks.byname mastername ipnodes.byaddr mastername ipnodes.byname mastername hosts.byaddr mastername hosts.byname mastername group.bygid mastername group.byname mastername passwd.byuid mastername passwd.byname mastername ypservers mastername On an NIS network with master server whose hostname is mammoth, the mastername is replaced by the hostname mammoth. If the output is not displayed, see ypwhich (1).
IP_address address_mask specifies the Internet address of an NIS server or the subnet of an NIS server from which the client accepts NIS information. indicates the important bits in the IP_address field. If a bit is set in the address_mask field, the corresponding bit in the source address of any address of an NIS server must match the same bit in the IP_address field. Example 5-1 Configuring Safe Servers for an NIS Client Example 5-1 displays how to configure safe servers for an NIS client.
Binding an NIS Client to a Server on a Different Subnet This section describes how to bind an NIS client to an NIS server on a different subnet or to a specific server on the same subnet. To bind an NIS client to any of the specified NIS servers on a different subnet, complete the following steps: 1. 2. Log in to the NIS client as a superuser.
6 Troubleshooting NIS This chapter discusses the following error messages and error conditions that you may encounter with suggested solutions: • • • • • “The NIS Server does not Respond” (page 59) “User Cannot Log In” (page 60) “Unknown Host” (page 61) “An NIS Client Cannot Bind to a Server” (page 62) “NIS Returns Incorrect Information” (page 62) The NIS Server does not Respond If the message “NIS Server Not Responding” is displayed, complete the following steps: 1.
User Cannot Log In If the user cannot login, complete the following steps: 1. 2. Verify whether you have entered the correct user ID and password. If you have recently changed passwords, log in using the old password. If you can log in using the old password, follow these steps: a. Run the ps -ef command on the NIS master server to ensure that the yppasswdd daemon is running. If it is not, run the following command to start all NIS server processes: # /sbin/init.d/nis.server start b.
b. c. d. e.
This command transfers the hosts database from the NIS master server to the server where you issue the command. 4. If the NIS client is bound to a slave server, use the following procedure to ensure that the slave server is listed in the NIS master server’s ypservers database: a. Run the following command on the NIS client to determine the server to which the client is bound to: # /usr/bin/ypwhich b.
# /usr/bin/ypwhich -m mapname If the server does not respond, see “The NIS Server does not Respond” (page 59). 2. Log in as root to the NIS master server, and run the following command to check the contents of the appropriate NIS map: # /usr/bin/ypcat -k mapname If the map contents are not correct, edit the ASCII file from which the map is generated. Then, run the following commands to regenerate the map and replicate it to the slave servers: # cd /var/yp # /usr/ccs/bin/make mapname 3.
A Sample NIS Session This appendix describes the procedure to configure a sample NIS network. This appendix addresses the following topics: • “Configuring an NIS Master Server” (page 65) • “Configuring an NIS Slave Server” (page 67) • “Configuring an NIS Client” (page 68) Configuring an NIS Master Server To configure an NIS master server, complete the following steps: 1. Log in to a system on the NIS network. 2. Modify the /etc/rc.config.
next host to add: mammoth next host to add: ocelot next host to add: The current list of NIS servers looks like this: mammoth ocelot Is this correct? [y/n: y] There will be no further questions. The ypinit procedure takes 5 to 10 minutes to complete the configuration. The following output is displayed: Building the ypservers database... ypservers build complete.
Configuring an NIS Slave Server To configure an NIS slave server, complete the following steps: 1. Log in to the NIS slave server. 2. Set the following variables in the NIS slave server to modify the /etc/ rc.config.d/namesvrs file: NIS_MASTER_SERVER=0 NIS_SLAVE_SERVER=1 NIS_CLIENT=1 NIS_DOMAIN=marketing It is not mandatory to set the NIS_CLIENT=1 variable to configure the NIS slave server. 3.
# /usr/sbin/ypinit -c To bind the NIS client to a particular NIS server, construct a list of NIS servers. Add the names of NIS servers in order of preference, one server name on each line. When you have no more names to add, press Ctrl+d or the Enter key on an empty line.
next host to add: The current list of yp servers looks like this: mammoth ocelot Is this correct? [y/n: y] y Type y or n and press the Enter key to confirm the output. 4. Start the NIS client: # /sbin/init.d/nis.client start IMPORTANT: Ensure that the /etc/hosts file contains the appropriate entries for the NIS servers added above.
B NIS Configuration File /etc/rc.config.d/namesvrs The /etc/rc.config.d/namesvrs file is the main NIS configuration file, through which NIS services can be enabled or disabled, and appropriate options can be provided for the NIS service. It also contains a list of the NIS maps built in the domain. The following lists the/etc/rc.config.d/namesvrs file: # # @(#)B.11.31_LR namesvrs $Revision: $ # # (C) Copyright 1998, 2000-2006 Hewlett-Packard Development Company, L.P.
# NIS_MASTER_SERVER=0 NIS_SLAVE_SERVER=0 NIS_CLIENT=0 NIS_DOMAIN= MAX_NISCHECKS=2 YPSERV_OPTIONS="" YPBIND_OPTIONS="" YPPASSWDD_OPTIONS="/etc/passwd -m passwd PWFILE=/etc/passwd" KEYSERV_OPTIONS="" YPUPDATED_OPTIONS="" YPXFRD_OPTIONS="" YPSET_ADDR="" LONGNAMES_OPTIONS="group.bygid.dir group.bygid.pag group.byname.dir \ group.byname.pag hosts.byaddr.dir hosts.byaddr.pag \ hosts.byname.dir hosts.byname.pag networks.byaddr.dir \ networks.byaddr.pag networks.byname.dir networks.byname.pag \ passwd.byname.
C Using NIS in Compat Mode This appendix describes how to use the Compatibility Mode function. The Compat Mode can be used to control the name services that are used to obtain user and group information. If you specify compat as a name service for the passwd: and group: entries in the /etc/nsswitch.conf file, then NIS consults the local /etc/passwd or /etc/group file. Any entries in the /etc/passwd or /etc/group file beginning with a plus (+) or a minus (-) sign directs the lookup to the NIS server.
-@bears:::::: +@documentation:::::: -@marketing:::::: These lines result in searching the NIS database for users from the documentation netgroup. Access is denied for users from the documentation and marketing netgroup. For more information about the /etc/passwd file, see passwd((4)). Editing the Slave Server's passwd File in Compat Mode • • HP recommends you to remove all users from the /etc/passwd file except the root user and the system entries required for your system to boot and function properly.
Editing the group File for Compat Mode • • HP recommends you to remove all groups from the /etc/group file except the group entries required for your system to boot and function properly. The /etc/nsswitch.nis file is the Name Service Switch configuration file provided for the NIS server. The /etc/nsswitch.nis file allows your host to check its local /etc/group file and then continue to the NIS group map if the requested information is not in the local file.
Index + (plus sign) in group file, 73 /etc/rc.config.
ypbind, 16 nis.client script, 30, 31, 54, 56, 57, 62 nis.
