1ypfiles(4) File Formats ypfiles(4)
2
6 ypfiles - Network Information Service Version 2, formerly knows as YP
7
9 The NIS network information service uses a distributed, replicated
10 database of dbm files , in ASCII form, that are contained in the
11 /var/yp directory hierarchy on each NIS server.
12 A dbm database served by the NIS server is called a NIS map. A NIS
15 domain is a subdirectory of /var/yp that contains a set of NIS maps on
16 each NIS server.
17 Standard nicknames are defined in the file /var/yp/nicknames. These
20 names can be used in place of the full map name in the ypmatch and
21 ypcat commands. Use the command ypwhich -x to display the current set
22 of nicknames. Use the command ypwhich -m to display all the available
23 maps. Each line of the nickname file contains two fields separated by
24 white space. The first field is the nickname, and the second field is
25 the name of the map that it expands to. The nickname cannot contain a
26 ".".
27 NIS to LDAP (N2L)
29 If the /var/yp/NISLDAPmapping configuration file is present, the NIS
30 server operates in NIS to LDAP (N2L) mode. In this mode, NIS maps are
31 stored in a new set of DBM files, prepended by the LDAP_ prefix, at
32 /var/yp/domainename. These files are used as a cache backed by informa‐
33 tion from an LDAP server. Additional DBM files are created in the same
34 directory to hold the cache's TTL values.
35 N2L mode enables NIS clients to be supported in an LDAP environment.
38 In N2L mode, the old style DBM files, NIS source files, and the
41 ypmake(1M) utility have to role. They are retained to enable easy con‐
42 version back to the traditional mode, if required.
43 Converting from N2L to Traditional NIS
45 When NIS is operating in N2L mode, it uses a new set of NIS maps with
46 an LDAP_ prefix, based on the contents of the LDAP DIT. The NIS source
47 files are unused and become out of date. If you wish to convert back to
48 the traditional NIS mode, the N2L configuration file should be deleted.
49 The system will then return to using the standard map files. Option‐
50 ally, the N2L mode map files, /var/yp/*/LDAP_* can also be deleted.
51 If you want to run the system in traditional mode with information
54 based on the DIT, then the NIS source files must be regenerated based
55 on the N2L maps. To regenerate the NIS source files based on the N2L
56 maps, run ypmap2src(1M).
57 NIS+
59 NIS+ also provides a NIS service when it runs in YP-compatibility mode.
60 See NIS+[22m(1) and rpc.nisd(1M). NIS+, in any mode, cannot be run on the
61 same system as ypserv, whether ypserv is in traditional or N2L mode.
62
64 /var/yp
65 Directory containing NIS configuration files.
67 /var/yp/binding
70 Stores the information required to bind the NIS client to the NIS
72 server.
73 /var/yp/binding/ypdomain/ypservers
76 Contains the servers to which the NIS client is allowed to bind.
78 /var/yp/Makefile
81 Builds the NIS ndbm databases.
83 /var/yp/nicknames
86 Nicknames file.
88 /var/yp/securenets
91 Defines the hosts and networks that are granted access to informa‐
93 tion in the served domain. This file is read at startup time by
94 ypserv and ypxfrd.
95 /var/yp/ypdomain
98 Directory containing ndbm databases.
100 /var/yp/NISLDAPmapping
103 NIS to LDAP configuration file
105 /var/yp/*/LDAP_*
108 NIS to LDAP mode map files
110
113 ldap(1), NIS+[22m(1), makedbm(1M), nisaddent(1M), nissetup(1M),
114 rpc.nisd(1M), ypbind(1M), ypinit(1M), ypmake(1M), ypmap2src(1M),
115 ypserv(1M), ypxfrd(1M), ndbm(3C), ypclnt(3NSL)
116
118 The NIS+ server, rpc.nisd, when run in "YP-compatibility mode", can
119 support NIS clients only for the standard NIS maps listed below, pro‐
120 vided that it has been set up to serve the corresponding NIS+ tables
121 using nissetup(1M) and nisaddent(1M). The NIS+ server should serve the
122 directory with the same name (case sensitive) as the domainname of the
123 NIS client. NIS+ servers use secure RPC to verify client credentials
124 but the NIS clients do not authenticate their requests using secure
125 RPC. Therefore, NIS clients can look up the information stored by the
126 NIS+ server only if the information has "read" access for an unauthen‐
127 ticated client, that is, one with nobody NIS+ credentials.
128 NIS maps NIS+ tables
130 passwd.byname passwd.org_dir
133 passwd.byuid passwd.org_dir
136 group.byname group.org_dir
139 group.bygid group.org_dir
142 publickey.byname cred.org_dir
145 hosts.byaddr hosts.org_dir
148 hosts.byname hosts.org_dir
151 mail.byaddr mail_aliases.org_dir
154 mail.aliases mail_aliases.org_dir
157 services.byname services.org_dir
160 services.byservicename services.org_dir
163 rpc.bynumber rpc.org_dir
166 rpc.byname rpc.org_dir
169 protocols.bynumber protocols.org_dir
172 protocols.byname protocols.org_dir
175 networks.byaddr networks.org_dir
178 networks.byname networks.org_dir
181 netmasks.byaddr netmasks.org_dir
184 ethers.byname ethers.org_dir
187 ethers.byaddr ethers.byname
190 bootparams bootparams
193 auto.master auto_master.org_dir
196 auto.home auto_home.org_dir
199 auto.direct auto_direct.org_dir
202 auto.src auto_src.org_dir
205SunOS 5.11 24 Nov 2003 ypfiles(4)