>
>> If the cache is invalid SSS will, obviously, go back to the source and
>> return the information there, however, bizarrely, if the original
>> source doesn't have the information (like when a user is deleted) the
>> cached information is still returned. That cached information is
>> retained
On Mon, 2018-08-06 at 19:55 -0700, Gordon Messmer wrote:
> On 08/06/2018 03:16 AM, Pete Biggs wrote:
> > If the cache is invalid SSS will, obviously, go back to the source and
> > return the information there, however, bizarrely, if the original
> > source doesn't have the information (like when a
> If the cache is invalid SSS will, obviously, go back to the source and
> return the information there, however, bizarrely, if the original
> source doesn't have the information (like when a user is deleted) the
> cached information is still returned. That cached information is
> retained for
On 08/06/2018 03:16 AM, Pete Biggs wrote:
If the cache is invalid SSS will, obviously, go back to the source and
return the information there, however, bizarrely, if the original
source doesn't have the information (like when a user is deleted) the
cached information is still returned. That
On Mon, 6 Aug 2018, Pete Biggs wrote:
I have a large number of CentOS machines (both 6 & 7) getting account
information from an LDAP database using SSSD. It all works fine and is
fairly reliable.
However, I'm having problems with persuading the caching system to
forget about users when they
I have a large number of CentOS machines (both 6 & 7) getting account
information from an LDAP database using SSSD. It all works fine and is
fairly reliable.
However, I'm having problems with persuading the caching system to
forget about users when they are deleted from LDAP.
I know about
6 matches
Mail list logo
