On Tue, Apr 14, 2015 at 10:33:18AM +0200, Thomas HUMMEL wrote:
On Mon, Apr 13, 2015 at 10:12:22PM +0200, Lukas Slebodnik wrote:
> You can disable fast memory cache if environment variable SSS_NSS_USE_MEMCACHE
> is set to no. The environment variable need to be set on client side (the
> process which call getpw*/getgr*).
Yes thank you, we discovered that a moment after we posted the message ;-)
> But I do not expect any problem with memory cache. The problem seems to be on
> responder side.
Why do you say that ? I mean can't the problem be on the backend side ? We
suspect some kind of race condition because we can only (deterministically)
reproduce the problem with slurm which spawns many processes in the same
Perhaps, maybe the backend is signalling to the frontend too soon to
check the cache again after the inital update.
But I'm not sure how to help you without a local reproducer :-/