On Tue, 2016 May 24 20:47+0200, Arthur de Jong wrote: > > I'm not really sure what triggers it but I also see this in the logs a > lot. I just ignore it. It could be that nscd makes it more difficult > to trigger because it sometimes also caches negative hits. > Furthermore, the application may be caching it.
Ah, yes, that makes sense. I'm using nscd as well. > > I claim ignorance as to why this request occurs (is this really > > supposed to return a list of all users?) > > No, I'm pretty sure it is some sort of lookup that is meant to return > nu users at all or a misconfiguration somewhere. If I can find what is doing this, should the behavior be considered a bug? (I'd be happy to file a report, as long as the maintainer is not likely to respond with "working as designed, closing.") > To not report it as an invalid name you could set validnames to > > /^[a-z0-9._@$()*]([a-z0-9._@$() \\~-]*[a-z0-9._@$()~-])?$/i > > but that is a bit ugly and it results in a useless LDAP search > each time. Yes, I'd want to avoid the extra network chatter (and server load, once you're talking about many clients).
