On Wed, Jan 16, 2013 at 10:54:43AM -0500, Simo Sorce wrote:
> On Tue, 2013-01-15 at 15:23 +0100, Jakub Hrozek wrote:
> > On Tue, Jan 15, 2013 at 08:27:32AM -0500, Simo Sorce wrote:
> > > On Tue, 2013-01-15 at 09:02 +0100, Jakub Hrozek wrote:
> > > > https://fedorahosted.org/sssd/ticket/1757
> > > >
On Tue, 2013-01-15 at 15:23 +0100, Jakub Hrozek wrote:
> On Tue, Jan 15, 2013 at 08:27:32AM -0500, Simo Sorce wrote:
> > On Tue, 2013-01-15 at 09:02 +0100, Jakub Hrozek wrote:
> > > https://fedorahosted.org/sssd/ticket/1757
> > >
> > > When the user entry was missing completely after initgroups, w
On Tue, Jan 15, 2013 at 08:27:32AM -0500, Simo Sorce wrote:
> On Tue, 2013-01-15 at 09:02 +0100, Jakub Hrozek wrote:
> > https://fedorahosted.org/sssd/ticket/1757
> >
> > When the user entry was missing completely after initgroups, we would
> > never invalidate the user entry from cache. This led
On Tue, 2013-01-15 at 09:02 +0100, Jakub Hrozek wrote:
> https://fedorahosted.org/sssd/ticket/1757
>
> When the user entry was missing completely after initgroups, we would
> never invalidate the user entry from cache. This led to dangling cache
> entried in memory cache if the user was removed fr
https://fedorahosted.org/sssd/ticket/1757
When the user entry was missing completely after initgroups, we would
never invalidate the user entry from cache. This led to dangling cache
entried in memory cache if the user was removed from the server while
still being in memory cache.
>From 71cceb360a