Re: Understanding nscd and caching
[Date Prev][Date Next] [Thread Prev][Thread Next]Re: Understanding nscd and caching
- From: Matt Hughes <hughes.matt [at] gmail.com>
- To: Arthur de Jong <arthur [at] arthurdejong.org>, nss-pam-ldapd-users [at] lists.arthurdejong.org
- Subject: Re: Understanding nscd and caching
- Date: Thu, 25 Sep 2014 11:16:40 -0400
I can see in the nscd logs that it is getting hit for host resolution, but it doesn’t ever seem to be getting hit for passwords. Does my nsswitch.conf look right? Is ‘files, ldap’ good enough? I’ve seen examples online that use ‘cache’ as well, but I can’t seem to find any good documentation to confirm that. I did run nslcd with strace as you suggested but don’t see anything interesting. It is authorizing users as expected, but the problem is it’s getting hit with every request. I tried unscd but that did not appear to change behavior. On September 24, 2014 at 4:33:06 PM, Arthur de Jong (arthur [at] arthurdejong.org) wrote:
|
-- To unsubscribe send an email to nss-pam-ldapd-users-unsubscribe@lists.arthurdejong.org or see http://lists.arthurdejong.org/nss-pam-ldapd-users/
- Understanding nscd and caching,
Matt Hughes
- Re: Understanding nscd and caching,
Arthur de Jong
- Re: Understanding nscd and caching, Matt Hughes
- Re: Understanding nscd and caching, Trent W. Buck
- Re: Understanding nscd and caching,
Arthur de Jong
- Re: Understanding nscd and caching, Trent W. Buck
- Prev by Date: Re: Understanding nscd and caching
- Next by Date: Re: Understanding nscd and caching
- Previous by thread: Re: Understanding nscd and caching
- Next by thread: Re: Understanding nscd and caching