Greetings, Corinna Vinschen! >> >There's only one tiny problem. Whatever I think about the full >> >enumerate being right or wrong, I have this vague feeling that I'd like >> >to have this implemented fully at one point. My cat disapproves, but we >> >can't agree on everything, I guess. Another configuration option in >> >/etc/nsswitch.conf might comfort her. >> >> I don't know if this has been mentioned but would a cache help here, >> i.e., nscd? I think that's how Linux deals with this type of situation.
> Caching is wonderful for the usual requests for single entries from the > DB, and for this we have already two caches, the LSA cache and Cygwin's > own cache. But caching doesn't help at all when enumerating. > There's also the problem to rely on an external program. If it turns > out that the current implementation is too slow, I'm prepared to add > caching to cygserver to have a system-wide caching server, but Cygwin > shouldn't *require* that cygserver runs. And either way, it still > wouldn't help when enumerating all accounts. Another rock in the direction of caching. Caching security-relevant data 'en masse' is usually a not-so-good idea, and should be considered very carefully. Even for Linux, common recommendation is to disable nscd to improve security and reliability of the accounting data. -- WBR, Andrey Repin (anrdae...@yandex.ru) 13.02.2014, <15:36> Sorry for my terrible english... -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple