An Example for the normal configuration file for the Name Service Switch module: nssswitch.conf file:
# Copyright 2006 Sun Microsystems, Inc. All rights reserved.
# Use is subject to license terms.
# ident "@(#)nsswitch.ldap 1.10 06/05/03 SMI"
# An example file that could be copied over to /etc/nsswitch.conf; it
# uses LDAP in conjunction with files.
# "hosts:" and "services:" in this file are used only if the
# /etc/netconfig file has a "-" for nametoaddr_libs of "inet" transports.
# LDAP service requires that svc:/network/ldap/client:default be enabled
# and online.
# the following two lines obviate the "+" entry in /etc/passwd and /etc/group.
passwd: files ldap
group: files ldap
# consult /etc "files" only if ldap is down.
# Note that IPv4 addresses are searched for in all of the ipnodes databases
# before searching the hosts databases.
automount: files ldap
aliases: files ldap
# for efficient getservbyname() avoid ldap
services: files ldap
printers: user files ldap
auth_attr: files ldap
prof_attr: files ldap
# trusted networks
- tnrhtp: - The tnrhtp file contains templates that define sets of security attributes that apply to various host types.
- tnrhdb: - The tnrhdb file assigns templates from the tnrhtp file to hosts and networks.
- tnidb - The tnidb file specifies security attributes that apply to network interfaces.
- project: - The project identifier is an administrative identifier that is used to identify related work. The project identifier can be thought of as a workload tag equivalent to the user and group identifiers. A user or group can belong to one or more projects.
- auth_attr: - The auth_attr file can be used with other authorization sources, including the auth_attr NIS map and NIS+ table.
- prof_attr: - The prof_attr database stores the name, description, help file location, and authorizations that are assigned to rights profiles. The commands and security attributes that are assigned to rights profiles are stored in the exec_attr database.
- bootparams - The bootparams file contains a list of client entries that diskless clients use for booting. Diskless booting clients retrieve this information by issuing requests to a server running the rpc.bootparamd(1M) program. The bootparams file may be used in conjunction with or in place of other sources for the bootparams information.
There might be more information for this subject on one of the following: