Re: Naming service daemon check is extremely chatty
[Date Prev][Date Next] [Thread Prev][Thread Next]Re: Naming service daemon check is extremely chatty
- From: Berend De Schouwer <berend [at] deschouwer.co.za>
- To: Subu Ayyagari <subu.ayyagari [at] gmail.com>
- Cc: nss-pam-ldapd-users [at] lists.arthurdejong.org
- Subject: Re: Naming service daemon check is extremely chatty
- Date: Thu, 28 Aug 2014 11:02:12 +0200
On Thu, 28 Aug, 2014 at 6:06 , Subu Ayyagari <subu.ayyagari@gmail.com> wrote:
Anyone please ? Is use of 'nslcd -c' prohibited ?If there are a 100 accounts allowed tfor hostaccess, the nslcd check actually queries for each of the 100+ accounts before it gives out a success. This type of monitoring would be detrimental.Thoughts ?
I think it's only supposed to check the pidfile, and then quit.If it's speaking to nscd, it's doing that because of an nsswitch configuration. For me it does a total of one lookup (it's own hostname) through nscd.
It's probably triggered by cfg_init(), which you can probably move to after 'if (nslcd_checkonly)' in nslcd/nslcd.c.
-- To unsubscribe send an email to nss-pam-ldapd-users-unsubscribe@lists.arthurdejong.org or see http://lists.arthurdejong.org/nss-pam-ldapd-users/
- Naming service daemon check is extremely chatty,
Subu Ayyagari
- Re: Naming service daemon check is extremely chatty,
Subu Ayyagari
- Re: Naming service daemon check is extremely chatty, Berend De Schouwer
- Re: Naming service daemon check is extremely chatty,
Subu Ayyagari
- Re: Naming service daemon check is extremely chatty, Arthur de Jong
- Prev by Date: Re: backport 0.9.3-1 to debian 7
- Next by Date: [PATCH] don't log "No such object" errors when a user is not found
- Previous by thread: Re: Naming service daemon check is extremely chatty
- Next by thread: Re: Naming service daemon check is extremely chatty