1nischttl(1) User Commands nischttl(1)
2
3
4
6 nischttl - change the time to live value of a NIS+ object
7
9 nischttl [-AfLP] time name...
10
11
13 nischttl changes the time to live value (ttl) of the NIS+ objects or
14 entries specified by name to time. Entries are specified using indexed
15 names (see nismatch(1)).
16
17
18 The time to live value is used by object caches to expire objects
19 within their cache. When an object is read into the cache, this value
20 is added to the current time in seconds yielding the time when the
21 cached object would expire. The object may be returned from the cache
22 until the current time is earlier than the calculated expiration time.
23 When the expiration time has been reached, the object will be flushed
24 from the cache.
25
26
27 The time to live time may be specified in seconds or in days, hours,
28 minutes, seconds format. The latter format uses a suffix letter of d,
29 h, m, or s to identify the units of time. See the examples below for
30 usage.
31
32
33 The command will fail if the master NIS+ server is not running.
34
35
36 Setting a high ttl value allows objects to stay persistent in caches
37 for a longer period of time and can improve performance. However, when
38 an object changes, in the worst case, the number of seconds in this
39 attribute must pass before that change is visible to all clients. Set‐
40 ting a ttl value of 0 means that the object should not be cached at
41 all.
42
43
44 A high ttl value is a week, a low value is less than a minute. Pass‐
45 word entries should have ttl values of about 12 hours (easily allows
46 one password change per day), entries in the RPC table can have ttl
47 values of several weeks (this information is effectively unchanging).
48
49
50 Only directory and group objects are cached in this implementation.
51
53 The following options are supported:
54
55 -A Modify all tables in the concatenation path that match the search
56 criterion specified in name. This option implies the -P switch.
57
58
59 -f Force the operation and fail silently if it does not succeed.
60
61
62 -L Follow links and change the time to live of the linked object or
63 entries rather than the time to live of the link itself.
64
65
66 -P Follow the concatenation path within a named table. This option
67 only makes sense when either name is an indexed name or the -L
68 switch is also specified and the named object is a link pointing
69 to entries.
70
71
73 Example 1 Changing the ttl of an Object
74
75
76 The following example shows how to change the ttl of an object using
77 the seconds format and the days, hours, minutes, seconds format. The
78 ttl of the second object is set to 1 day and 12 hours.
79
80
81 example% nischttl 184000 object
82 example% nischttl 1d12h object
83
84
85
86 Example 2 Changing the ttl for a password Entry
87
88
89 This example shows how to change the ttl for a password entry.
90
91
92 example% nischttl 1h30m '[uid=99],passwd.org_dir'
93
94
95
96 Example 3 Changing the ttl of Entries Pointed to by a Link
97
98
99 The next two examples change the ttl of the object or entries pointed
100 to by a link, and the ttl of all entries in the hobbies table.
101
102
103 example% nischttl -L 12h linkname
104 example% nischttl 3600 '[],hobbies'
105
106
107
109 NIS_PATH If this variable is set, and the NIS+ name is not fully
110 qualified, each directory specified will be searched until
111 the object is found. See nisdefaults(1).
112
113
115 The following exit values are returned:
116
117 0 Successful operation.
118
119
120 1 Operation failed.
121
122
124 See attributes(5) for descriptions of the following attributes:
125
126
127
128
129 ┌─────────────────────────────┬─────────────────────────────┐
130 │ ATTRIBUTE TYPE │ ATTRIBUTE VALUE │
131 ├─────────────────────────────┼─────────────────────────────┤
132 │Availability │SUNWnisu │
133 └─────────────────────────────┴─────────────────────────────┘
134
136 NIS+[22m(1), nischgrp(1), nischmod(1), nischown(1), nisdefaults(1), nis‐
137 match(1), nis_objects(3NSL), attributes(5)
138
140 NIS+ might not be supported in future releases of the Solaris operating
141 system. Tools to aid the migration from NIS+ to LDAP are available in
142 the current Solaris release. For more information, visit
143 http://www.sun.com/directory/nisplus/transition.html.
144
145
146
147SunOS 5.11 2 Dec 2005 nischttl(1)