Configuration option to force namcd to only use cache

Resolution of users and groups fails after a period of time when using /etc/nsswitch.conf is configured to use nam (module used by LUM).
Utilities that require user and group resolution hang waiting for namcd to return a response (ssh, ls, ps, etc.)

A problem in the LDAP client on SLES causes namcd to mark the LDAP server as down.

This problem has been reported to development.

To work around this issue:

When using LUM version 2.2.0.4-1 or 2.2.0.6-1
Modify the /etc/init.d/namcd script so that the start section reflects the following:

sbin/startproc -p $NAMCD_PID_FILE $sbindir/namcd

to be:

/sbin/startproc -p $NAMCD_PID_FILE $sbindir/namcd -c

Restart namcd:
rcnamcd restart

When using LUM version 2.2.0.8-1 or later

Added the following line to the /etc/nam.conf:

cache-only=yes

The default is cache-only set to no.

Note:

enable-persistent-cache=yes

needs to be set in the /etc/nam.conf file for this configuration to work.

This configuration will force namcd to use it's cache file for resolution not query the LDAP server.