1YPSERV(8) YPSERV(8)
2
6 ypxfr - transfer NIS database from remote server to local host
7
9 /usr/lib64/yp/ypxfr [ -f ] [ -c ] [ -d target domain ]
10 [ -h source host ] [ -s source domain ]
11 [ -C taskid program-number ipaddr port ]
12 [ -p yp_path ] mapname ...
13
16 ypxfr copies an NIS database from one NIS server to the local host by
17 using the NIS service. ypxfr is generally invoked by ypinit or by
18 ypserv, when ypserv receives a map transfer request from yppush. It
19 creates a temporary map in the directory /var/yp/domain (this direc‐
20 tory must already exist; domain is the default domainname for the
21 local host), fills it by getting the map's entries and fetches the map
22 parameters (master and order number). If the transfer was successful,
23 the old version of the map will be deleted and the temporary copy will
24 be moved into its place. Then, ypxfr will attempt to send a "clear
25 current map" request to the local ypserv.
26 If run interactively, ypxfr writes its output to stderr. However, if
28 it is invoked without a controlling terminal, it will log the output to
29 syslog.
30 ypxfr is used primarily in environments where several NIS servers are
32 in use. For all maps, you have a NIS master server, which maintains a
33 canonical copy of the NIS map, and all the other servers, the NIS
34 slaves, copy the new version of the map from the master whenever a
35 update was made. Normally, you have one NIS master for all maps.
36 In order to maintain consistency across all NIS servers, ypxfr can be
38 run periodically in a cron job. Maps which change infrequently need
39 only be updated once a day (preferably late at night when system usage
40 is lowest), where those with frequent changes (such as passwd.byname
41 and passwd.byuid ) should be updated perhaps once every hour. Examples
42 are in /usr/lib64/yp: ypxfr_1perday, ypxfr_2perday, and ypxfr_1perhour.
43 They can serve as reasonable first cuts.
44 Normally all updates should be propagated by yppush when /var/yp/Make‐
46 file is run on the NIS master server, however it is a good practice on
47 large networks where possible outages could cause NIS slaves to fall
48 out of sync with the master.
49
53 The following options are supported:
54 -f Force a map transfer. Normally, ypxfr will not transfer a map if
56 it determines that the NIS master's copy is not newer than the
57 existing copy already on the local host. This flag forces a
58 transfer regardless of which server's version is more recent.
59 -c Do not send a "clear current map" request to the ypserv process
61 running on the local host. This flag is normally used when
62 invoking ypxfr by ypinit or if ypserv is not running locally
63 at the time you are running ypxfr. Otherwise, ypxfr will com‐
64 plain that it cannot talk to the local ypserv, and the transfer
65 will fail.
66 -d domain
68 Specify a domain other than the default NIS domain.
69 -h source host
71 Get the map from host, regardless of what the map says the mas‐
72 ter is. If host is not specified, ypxfr asks the NIS service
73 for the name of the master, and tries to get the map from there.
74 This option is used to insure that ypxfr only copies maps from
75 the NIS master server.
76 -s source domain
78 Specify a source domain from which to transfer a map that should
79 be the same across domains.
80 -C taskid progam-number ipaddr port
82 This option is only for use by ypserv . When ypserv invokes
83 ypxfr, it specifies that ypxfr should call back a yppush process
84 at the host with IP address ipaddr, registered as program number
85 progam-number, listening on port port, and waiting for a
86 response to transaction taskid.
87 -p yp_path
89 Change the directory for the maps to yp_path/[domainname]/, the
90 default is /var/yp/[domainname].
91 mapname
93 One or more names of the map to transfer.
94
96 /var/yp/[domainname]/[maps]
97
99 ypserv(8), yppush(8), ypinit(8), cron(8), crontab(5)
100
102 Thorsten Kukuk <kukuk@suse.de>
103YP Server August 2001 YPSERV(8)