Re: Naming service daemon check is extremely chatty

[Subu Ayyagari <subu.ayyagari [at] gmail.com>]

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 ?

On Fri, Aug 15, 2014 at 1:34 AM, Subu Ayyagari <subu.ayyagari [at] gmail.com> wrote:

Hi all, 

We are using the daemon check ( nslcd -c ) to monitor the service. 

But what we find is this is extremely chatty. It actually queries every account and returns success in the end.

Additionally it discards any local caching (nscd) and checks all accounts all over again - depending on monitoring frequency.

Is this a known behavior or a bug ? 

Why not check say one account instead of checking all accounts ? 

thoughts ? 

- Subu

subu.ayyagari [at] gmail.com

-- 
To unsubscribe send an email to
nss-pam-ldapd-users-unsubscribe@lists.arthurdejong.org or see
http://lists.arthurdejong.org/nss-pam-ldapd-users/