LX0-104 · Question #134
A user is unable to login on a workstation where NSCD was configured BEFORE the pam_ldap and nss_ldap modules. What should be done to fix this problem?
The correct answer is B. Restart the nscd daemon. To fix a login issue after configuring LDAP modules when NSCD was already running, the nscd daemon must be restarted.
Question
Options
- ARestart the NSS server.
- BRestart the nscd daemon.
- CRestart the PAM server.
- Dnscd is incompatible with OpenLDAP and should be disabled.
- Enscd must be started with the -ldap=yes option.
How the community answered
(63 responses)- A13% (8)
- B76% (48)
- C3% (2)
- D2% (1)
- E6% (4)
Why each option
To fix a login issue after configuring LDAP modules when NSCD was already running, the `nscd` daemon must be restarted.
There is no single 'NSS server' to restart; NSS is a local system library configuration.
When `pam_ldap` and `nss_ldap` modules are configured after `nscd` has started, `nscd`'s cache will not contain the new LDAP lookup configurations. Restarting the `nscd` daemon forces it to re-read the Name Service Switch (NSS) configuration files and rebuild its cache, thereby incorporating the LDAP user and group information.
There is no 'PAM server'; PAM is a framework and modules, not a standalone server daemon that requires a restart in this context.
NSCD is compatible with OpenLDAP; its purpose is to cache lookups, including those from LDAP, to improve performance.
NSCD does not have an `-ldap=yes` option; its configuration is primarily through `/etc/nscd.conf` and interaction with NSS.
Concept tested: NSCD cache and LDAP integration
Topics
Community Discussion
No community discussion yet for this question.