1nis_ping(3NSL) Networking Services Library Functions nis_ping(3NSL)
2
3
4
6 nis_ping, nis_checkpoint - NIS+ log administration functions
7
9 cc [ flag ... ] file ... -lnsl [ library ... ]
10 #include <rpcsvc/nis.h>
11
12
13
14 void nis_ping(nis_name dirname, uint32_t utime, nis_object *dirobj);
15
16
17 nis_result *nis_checkpoint(nis_name dirname);
18
19
21 nis_ping() is called by the master server for a directory when a change
22 has occurred within that directory. The parameter dirname identifies
23 the directory with the change. If the parameter dirobj is NULL, this
24 function looks up the directory object for dirname and uses the list of
25 replicas it contains. The parameter utime contains the timestamp of the
26 last change made to the directory. This timestamp is used by the repli‐
27 cas when retrieving updates made to the directory.
28
29
30 The effect of calling nis_ping() is to schedule an update on the
31 replica. A short time after a ping is received, typically about two
32 minutes, the replica compares the last update time for its databases to
33 the timestamp sent by the ping. If the ping timestamp is later, the
34 replica establishes a connection with the master server and request
35 all changes from the log that occurred after the last update that it
36 had recorded in its local log.
37
38
39 nis_checkpoint() is used to force the service to checkpoint information
40 that has been entered in the log but has not been checkpointed to disk.
41 When called, this function checkpoints the database for each table in
42 the directory, the database containing the directory and the transac‐
43 tion log. Care should be used in calling this function since directo‐
44 ries that have seen a lot of changes may take several minutes to check‐
45 point. During the checkpointing process, the service will be unavail‐
46 able for updates for all directories that are served by this machine
47 as master.
48
49
50 nis_checkpoint() returns a pointer to a nis_result structure. See
51 nis_tables(3NSL). This structure should be freed with nis_freere‐
52 sult(). See nis_names(3NSL). The only items of interest in the returned
53 result are the status value and the statistics.
54
56 See attributes(5) for descriptions of the following attributes:
57
58
59
60
61 ┌─────────────────────────────┬─────────────────────────────┐
62 │ ATTRIBUTE TYPE │ ATTRIBUTE VALUE │
63 ├─────────────────────────────┼─────────────────────────────┤
64 │MT-Level │MT-Safe │
65 └─────────────────────────────┴─────────────────────────────┘
66
68 nislog(1M), nis_names(3NSL), nis_tables(3NSL), nisfiles(4),
69 attributes(5)
70
72 NIS+ might not be supported in future releases of the Solaris operating
73 system. Tools to aid the migration from NIS+ to LDAP are available in
74 the current Solaris release. For more information, visit
75 http://www.sun.com/directory/nisplus/transition.html.
76
77
78
79SunOS 5.11 10 Nov 2005 nis_ping(3NSL)