[SSSD] [PATCH] Set Cache expiration in providers

Stephen Gallagher sgallagh at redhat.com
Tue Oct 27 13:21:02 UTC 2009


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 10/24/2009 02:10 PM, Simo Sorce wrote:
> I came to the conclusion that expiration time should really be a backend
> property, not a frontend one.
> 
> The frontend can always decide to not obey the cache expiration time and
> force an update of course. This is in fact happens as part of the midway
> refresh strategy or in the pam service where we always make sure to
> fetch entries from the source on login.
> 
> Simo.
> 
> 
> 
> 
> _______________________________________________
> sssd-devel mailing list
> sssd-devel at lists.fedorahosted.org
> https://fedorahosted.org/mailman/listinfo/sssd-devel

Code looks good, but it won't apply on master. Please rebase and I will
test and ack.

- -- 
Stephen Gallagher
RHCE 804006346421761

Looking to carve out IT costs?
www.redhat.com/carveoutcosts/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAkrm87oACgkQeiVVYja6o6Ni7gCbB/Y2nIey/y4tQfCVtx2AkhtF
1S4AnjSt+ayMxfqUpVSWi/NLD8KBKFgc
=ULqN
-----END PGP SIGNATURE-----



More information about the sssd-devel mailing list