1ypmap2src(1M) System Administration Commands ypmap2src(1M)
2
6 ypmap2src - convert NIS maps to NIS source files
7
9 /usr/lib/netsvc/yp/ypmap2src [-t]
10 [ [-c custom-map-name]]... [-d domain] -o output-directory
11 [ [ source-file]]...
12
15 Use the ypmap2src utility to convert standard NIS maps to approxima‐
16 tions of the equivalent NIS source files. This utility functions like
17 the reverse of ypmake(1M).
18 The primary use for ypmap2src is to convert from a NIS server that uses
21 the NIS to LDAP(N2L) transition mechanism, which does not use NIS
22 source files, to traditional NIS, where source files are required. The
23 ypmap2src utility is also used by NIS administrators who wish to dis‐
24 cover the contents of NIS maps for which the sources are not available.
25 Generally, this operation is not necessary. More often, administrators
28 will switch from traditional NIS to N2L in anticipation of the eventual
29 transition to LDAP naming. When this switch is made, authoritative
30 information is moved into the LDAP DIT, and the NIS sources have no
31 further role. N2L supports NIS clients until such time as they can be
32 converted to LDAP, and the NIS service suspended.
33 The ypmap2src utility does not guarantee that the files that are gener‐
36 ated are identical to the original NIS source files. Some information
37 might have been thrown away by ypmake and cannot be recovered. N2L also
38 might have updated the maps to reflect changes made by LDAP clients. It
39 is essential that the sources generated are checked to confirm no prob‐
40 lems have occurred.
41 Per entry comment fields, from existing source files, are not merged
44 into source files generated by ypmap2src. If a user wishes N2L to main‐
45 tain comment information, then the NISLDAPmapping configuration file
46 should be modified so that the comment fields are mapped into LDAP.
47 This will ensure that the comments are visible to native LDAP clients
48 and present in the N2L map files.
49 When ypmap2src is run, it will take up-to-date comments from the map
52 file and insert them into the NIS source file generated.
53 Handling Custom Maps
55 ypmap2src only knows about the standard NIS maps and standard source to
56 map conversion. If an advanced user has changed these, that is, the
57 user has modified the NIS makefile, the equivalent changes must also be
58 made to the ypmap2src script.
59
61 ypmap2src supports the following options:
62 -c Specifies that custom-map-name should be converted to
64 a source file by running makedbm -u on it.
65 This is a short cut so that simple custom maps can be
66 handled without editing ypmap2src.
67 -d domain-name Specifies the domain to convert. The domain-name can
70 be a fully qualified file path, such as
71 /var/yp/a.b.c, or just a domain name, a.b.c.
72 In the latter case, ypmaptosrc looks in /var/yp for
73 the domain directory.
74 -o dest Specifies the destination directory for the con‐
77 verted files. A directory other than /etc should be
78 specified. The maps generated are copied to the cor‐
79 rect location, /etc, /etc/security or other source
80 directory, as appropriate.
81 -t Specifies that traditional NIS maps, without N2L's
84 LDAP_ prefix, should be converted. By default, maps
85 with the LDAP_ prefix are converted.
86
89 ypmap2src supports the following operands:
90 source-file Lists the standard source files to convert. If this
92 option is not given, then all the standard source files,
93 plus any custom files pecified by the -c option, are
94 converted.
95
98 See attributes(5) for descriptions of the following attributes:
99 ┌─────────────────────────────┬─────────────────────────────┐
104 │ ATTRIBUTE TYPE │ ATTRIBUTE VALUE │
105 ├─────────────────────────────┼─────────────────────────────┤
106 │Availability │SUNWypu │
107 ├─────────────────────────────┼─────────────────────────────┤
108 │Interface Stability │Obsolete │
109 └─────────────────────────────┴─────────────────────────────┘
110
112 ypmake(1M), ypserv(1M), NISLDAPmapping(4), attributes(5)
113SunOS 5.11 10 Apr 2003 ypmap2src(1M)