nischttl(1) nischttl(1)
NAME [Toc] [Back]
nischttl - change the time to live value of an NIS+ object
SYNOPSIS [Toc] [Back]
nischttl [ -AfLP ] time name...
DESCRIPTION [Toc] [Back]
nischttl changes the time to live value (ttl) of the NIS+ objects or
entries specified by name to time. Entries are specified using
indexed names (see nismatch(1)).
The time to live value is used by object caches to expire objects
within their cache. When an object is read into the cache, this value
is added to the current time in seconds yielding the time when the
cached object would expire. The object may be returned from the cache
as long as the current time is earlier than the calculated expiration
time. When the expiration time has been reached, the object will be
flushed from the cache.
The time to live time may be specified in seconds or in days, hours,
minutes, seconds format. The latter format uses a suffix letter of d,
h, m, or s to identify the units of time. See the examples below for
usage.
The command will fail if the master NIS+ server is not running.
Options [Toc] [Back]
-A Modify all tables in the concatenation path that match the search
criterion specified in name. This option implies the -P switch.
-f Force the operation and fail silently if it does not succeed.
-L Follow links and change the time to live of the linked object or
entries rather than the time to live of the link itself.
-P Follow the concatenation path within a named table. This option
only makes sense when either name is an indexed name or the -L
switch is also specified and the named object is a link pointing
to entries.
Notes [Toc] [Back]
Setting a high ttl value allows objects to stay persistent in caches
for a longer period of time and can improve performance. However,
when an object changes, in the worst case, the number of seconds in
this attribute must pass before that change is visible to all clients.
Setting a ttl value of 0 means that the object should not be cached at
all.
A high ttl value is a week, a low value is less than a minute.
Password entries should have ttl values of about 12 hours (easily
allows one password change per day), entries in the RPC table can have
Hewlett-Packard Company - 1 - HP-UX 11i Version 2: August 2003
nischttl(1) nischttl(1)
ttl values of several weeks (this information is effectively
unchanging).
Only directory and group objects are cached in this implementation.
EXAMPLES [Toc] [Back]
Change the ttl of an object using the seconds format and the days,
hours, minutes, seconds format (the ttl of the second object is set to
1 day and 12 hours):
nischttl 184000 object
nischttl 1d12h object
Change the ttl for a password entry:
nischttl 1h30m '[uid=99],passwd.org_dir'
Change the ttl of the object or entries pointed to by a link, and the
ttl of all entries in the hobbies table:
nischttl -L 12h linkname
nischttl 3600 '[],hobbies'
EXTERNAL INFLUENCES [Toc] [Back]
Environment Variables
NIS_PATH If this variable is set and the NIS+ name is not fully
qualified, each directory specified will be searched
until the object is found (see nisdefaults(1)).
RETURN VALUE [Toc] [Back]
nischttl returns 0 on success and 1 on failure.
WARNINGS [Toc] [Back]
HP-UX 11i Version 2 is the last HP-UX release on which NIS+ is
supported.
LDAP is the recommended replacement for NIS+. HP fully supports the
industry standard naming services based on LDAP.
AUTHOR [Toc] [Back]
nischttl was developed by Sun Microsystems, Inc.
SEE ALSO [Toc] [Back]
nis+(1), nischgrp(1), nischmod(1), nischown(1), nisdefaults(1),
nis_objects(3N).
Hewlett-Packard Company - 2 - HP-UX 11i Version 2: August 2003 [ Back ] |