On Thu, 2013-10-31 at 15:30 +0100, Axel Beckert wrote: > it would be nice if nslcd could be configured to not log any > occurrences of "request denied by validnames option" or similar less > critical but potentially noisy logging.
Thanks for reporting this bug. > Oct 31 14:36:42 snidget logger: foo=bar > Oct 31 14:36:42 snidget nslcd[19433]: [3ceb7b] <passwd="foo=bar"> request > denied by validnames option > Oct 31 14:36:42 snidget nslcd[19433]: [ac75da] <passwd="passwd="foo=bar"> > request denied by validnames option > Oct 31 14:36:42 snidget nslcd[19433]: [dd5ee7] > <passwd="passwd="passwd="foo=bar"> request denied by validnames option > Oct 31 14:36:42 snidget nslcd[19433]: [e23ed4] > <passwd="passwd="passwd="passwd="foo=bar> request denied by validnames option This is actually a bit funny ;) > But I still would be happy if there would be a way to suppress these > less critical messages completely. Maybe adding some log level setting > or similar. Indeed, nslcd can log several warnings that will be annoying if they happen too often. In #567099 the proposed solution is to implement rate limiting of such errors (actually the bug is regarding log entries about problematic data in LDAP but the principal is the same). If anyone is prepared to write a patch for this, I'll ensure that it gets integrated. There is already a cache-like structure in nslcd for caching dn to uid lookups. Something similar could be made for looking up certain warnings. Thanks, -- -- arthur - adej...@debian.org - http://people.debian.org/~adejong --
signature.asc
Description: This is a digitally signed message part
