1nisping(1M) System Administration Commands nisping(1M)
2
3
4
6 nisping - send ping to NIS+ servers
7
9 /usr/lib/nis/nisping [-uf] [-H hostname] [-r | directory]
10
11
12 /usr/lib/nis/nisping -C [-a] [-H hostname] [directory]
13
14
16 In the first line, the nisping command sends a ``ping'' to all repli‐
17 cas of an NIS+ directory. Once a replica receives a ping, it will check
18 with the master server for the directory to get updates. Prior to ping‐
19 ing the replicas, this command attempts to determine the last update
20 "seen" by a replica and the last update logged by the master. If these
21 two timestamps are the same, the ping is not sent. The -f (force)
22 option will override this feature.
23
24
25 Under normal circumstances, NIS+ replica servers get the new informa‐
26 tion from the master NIS+ server within a short time. Therefore, there
27 should not be any need to use nisping.
28
29
30 In the second line, the nisping -C command sends a checkpoint request
31 to the servers. If no directory is specified, the home domain, as
32 returned by nisdefaults(1), is checkpointed. If all directories, served
33 by a given server, have to be checkpointed, then use the -a option.
34
35
36 On receiving a checkpoint request, the servers would commit all the
37 updates for the given directory from the table log files to the data‐
38 base files. This command, if sent to the master server, will also send
39 updates to the replicas if they are out of date. This option is needed
40 because the database log files for NIS+ are not automatically check‐
41 pointed. nisping should be used at frequent intervals (such as once a
42 day) to checkpoint the NIS+ database log files. This command can be
43 added to the crontab(1) file. If the database log files are not check‐
44 pointed, their sizes will continue to grow.
45
46
47 If the server specified by the -H option does not serve the directory,
48 then no ping is sent.
49
50
51 Per-server and per-directory access restrictions may apply; see
52 nisopaccess(1). nisping uses NIS_CPTIME and NIS_PING (resync (ping) of
53 replicas), or NIS_CHECKPOINT (for checkpoint). Since the NIS_PING oper‐
54 ation does not return a status, the nisping command is typically unable
55 to indicate success or failure for resyncs.
56
58 -a Checkpoint all directories on the server.
59
60
61 -C Send a request to checkpoint, rather than a ping, to
62 each server. The servers schedule to commit all the
63 transactions to stable storage.
64
65
66 -H hostname Only the host hostname is sent the ping, checked for an
67 update time, or checkpointed.
68
69
70 -f Force a ping, even though the timestamps indicate there
71 is no reason to do so. This option is useful for debug‐
72 ging.
73
74
75 -r This option can be used to update or get status about
76 the root object from the root servers, especially when
77 new root replicas are added or deleted from the list.
78
79 If used without -u option, -r will send a ping request
80 to the servers serving the root domain. When the repli‐
81 cas receive a ping, they will update their root object
82 if needed.
83
84 The -r option can be used with all other options except
85 with the -C option; the root object need not be check‐
86 pointed.
87
88
89 -u Display the time of the last update; no servers are sent
90 a ping.
91
92
94 −1 No servers were contacted, or the server specified by the -H
95 switch could not be contacted.
96
97
98 0 Success.
99
100
101 1 Some, but not all, servers were successfully contacted.
102
103
105 Example 1 Using nisping
106
107
108 This example pings all replicas of the default domain:
109
110
111 example% nisping
112
113
114
115
116 Note that this example will not ping the org_dir and groups_dir subdi‐
117 rectories within this domain.
118
119
120
121 This example pings the server example which is a replica of the
122 org_dir.foo.com. directory:
123
124
125 example% nisping -H example org_dir.foo.com.
126
127
128
129
130 This example checkpoints all servers of the org_dir.bar.com. directory.
131
132
133 example% nisping -C org_dir.bar.com.
134
135
136
138 NIS_PATH If this variable is set, and the NIS+ directory name is not
139 fully qualified, each directory specified will be searched
140 until the directory is found.
141
142
144 See attributes(5) for descriptions of the following attributes:
145
146
147
148
149 ┌─────────────────────────────┬─────────────────────────────┐
150 │ ATTRIBUTE TYPE │ ATTRIBUTE VALUE │
151 ├─────────────────────────────┼─────────────────────────────┤
152 │Availability │SUNWnisu │
153 └─────────────────────────────┴─────────────────────────────┘
154
156 crontab(1), nisdefaults(1), nisopaccess(1), nislog(1M), nisfiles(4),
157 attributes(5)
158
160 NIS+ might not be supported in future releases of the Solaris operating
161 system. Tools to aid the migration from NIS+ to LDAP are available in
162 the current Solaris release. For more information, visit
163 http://www.sun.com/directory/nisplus/transition.html.
164
165
166
167SunOS 5.11 12 Dec 2001 nisping(1M)