NIS/LDAP Gateway Administrator's Guide

and the group map as these are often the largest and most enumerated maps. However, the more
maps you preload, the longer the NIS/LDAP Gateway takes to start up.
Use the preload_cache parameter in ypldapd.conf. For example, the following command specifies
preloading of the passwd.byname map and group.byname map:
preload_cache passwd.byname group.byname
For information on the preload_cache parameter see “Preload Maps into the Cache”.
NOTE: For best overall performance, you should turn off ypall_caching by setting the
ypall_caching parameter to "no" in the file ypldapd.conf and use preloaded maps instead. See
“Preload Maps into the Cache” for more information.
Setting the Frequency of Cache Refreshing
You can specify how often the cache is refreshed with the cache_dump_interval parameter as
described in “Cache Lifetime”. All preloaded maps will be refreshed periodically, as specified
by cache_dump_interval. Maps not preloaded will be flushed, not refreshed. Future client requests
will refill the cache.
The cache_dump_value you use depends on how often you want the cache to be updated, how
often information in your directory changes, and how large your preloaded maps are. The larger
the cache_dump_interval, the less frequently the preloaded maps in the cache will be updated.
The smaller the cache_dump_interval, the more frequently the preloaded maps in the cache will
be updated. If you or another user updates the directory, the preloaded maps will not reflect the
change until the cache is refreshed. ldappasswd, however, is a special case. When a user changes
their password, ldappasswd marks that password entry in the cache as stale.
One strategy is to set the cache_dump_interval to 60 if your maps are greater than 1 megabyte.
This will refresh the cache once an hour. If your maps are smaller then 1 megabyte, set the
cache_dump_interval to something less than an hour. The more maps you preload, the larger
your cache_dump_interval should be.
Forcing a Refresh of the Cache
You can use the following command to force a refresh of the preloaded maps in the cache:
kill -s SIGUSR2 $( cat /var/run/ypldapd.pid )
This assumes the file /var/run/ypldapd.pid contains the process identifier of the ypldapd daemon.
You configure this with the pidfile parameter in the configuration file as described under “PID
File”.
NOTE: The kill -s SIGUSR2 $( cat /var/run/ypldapd.pid ) command only applies
to HP-UX 11i version2.
NOTE: You can use the following command to log the cache statistics and state information
via syslog:
kill -s SIGUSR1 $( cat /var/run/ypldapd.pid )
This only applies to HP-UX 11i version2.
Troubleshooting
This section lists problems you may encounter, how to troubleshoot and solve them.
Troubleshooting 29