-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
There are several problems with how we determine what entries to purge from the cache during the cleanup task in 1.2.x. Rather than expend the energy trying to track them down, it makes sense to disable the cleanup task by default.
The only purpose of the cache cleanup is to keep disk usage down, but there should be no issue with disabling it. It's possible that there may be groups with no members hanging around, but this is not harmful.
- -- Stephen Gallagher RHCE 804006346421761
Delivering value year after year. Red Hat ranks #1 in value among software vendors. http://www.redhat.com/promo/vendor/
On Wed, Feb 09, 2011 at 12:21:00PM -0500, Stephen Gallagher wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
There are several problems with how we determine what entries to purge from the cache during the cleanup task in 1.2.x. Rather than expend the energy trying to track them down, it makes sense to disable the cleanup task by default.
The only purpose of the cache cleanup is to keep disk usage down, but there should be no issue with disabling it. It's possible that there may be groups with no members hanging around, but this is not harmful.
I think ldap_purge_cache_timeout is still missing in SSSDConfig.py.
bye, Sumit
Stephen Gallagher RHCE 804006346421761
Delivering value year after year. Red Hat ranks #1 in value among software vendors. http://www.redhat.com/promo/vendor/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iEYEARECAAYFAk1SzPwACgkQeiVVYja6o6MFBQCdHKjPc/Zoa3hbA61tsyMs56AX b5MAoJgn1xqO4x2SthCPpV7LtEraIROT =/VhA -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 02/10/2011 07:07 AM, Sumit Bose wrote:
On Wed, Feb 09, 2011 at 12:21:00PM -0500, Stephen Gallagher wrote: There are several problems with how we determine what entries to purge from the cache during the cleanup task in 1.2.x. Rather than expend the energy trying to track them down, it makes sense to disable the cleanup task by default.
The only purpose of the cache cleanup is to keep disk usage down, but there should be no issue with disabling it. It's possible that there may be groups with no members hanging around, but this is not harmful.
I think ldap_purge_cache_timeout is still missing in SSSDConfig.py.
It's missing from the translations, but it exists in sssd-ldap.conf
I don't want to break strings to fix this in 1.2.x.
- -- Stephen Gallagher RHCE 804006346421761
Delivering value year after year. Red Hat ranks #1 in value among software vendors. http://www.redhat.com/promo/vendor/
On Thu, Feb 10, 2011 at 02:38:16PM -0500, Stephen Gallagher wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 02/10/2011 07:07 AM, Sumit Bose wrote:
On Wed, Feb 09, 2011 at 12:21:00PM -0500, Stephen Gallagher wrote: There are several problems with how we determine what entries to purge from the cache during the cleanup task in 1.2.x. Rather than expend the energy trying to track them down, it makes sense to disable the cleanup task by default.
The only purpose of the cache cleanup is to keep disk usage down, but there should be no issue with disabling it. It's possible that there may be groups with no members hanging around, but this is not harmful.
I think ldap_purge_cache_timeout is still missing in SSSDConfig.py.
It's missing from the translations, but it exists in sssd-ldap.conf
I don't want to break strings to fix this in 1.2.x.
ok, valid point.
ACK
bye, Sumit
Stephen Gallagher RHCE 804006346421761
Delivering value year after year. Red Hat ranks #1 in value among software vendors. http://www.redhat.com/promo/vendor/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iEYEARECAAYFAk1UPqgACgkQeiVVYja6o6Ml8wCdHEkV6MNtbKRtcK2tVCuR+Lax IH8AoJrugz01FQ2fHcv53MteykQdw/bI =daBa -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 02/10/2011 02:59 PM, Sumit Bose wrote:
On Thu, Feb 10, 2011 at 02:38:16PM -0500, Stephen Gallagher wrote: On 02/10/2011 07:07 AM, Sumit Bose wrote:
On Wed, Feb 09, 2011 at 12:21:00PM -0500, Stephen Gallagher wrote: There are several problems with how we determine what entries to purge from the cache during the cleanup task in 1.2.x. Rather than expend the energy trying to track them down, it makes sense to disable the cleanup task by default.
The only purpose of the cache cleanup is to keep disk usage down, but there should be no issue with disabling it. It's possible that there may be groups with no members hanging around, but this is not harmful.
I think ldap_purge_cache_timeout is still missing in SSSDConfig.py.
It's missing from the translations, but it exists in sssd-ldap.conf
I don't want to break strings to fix this in 1.2.x.
ok, valid point.
ACK
Pushed to sssd-1-2
- -- Stephen Gallagher RHCE 804006346421761
Delivering value year after year. Red Hat ranks #1 in value among software vendors. http://www.redhat.com/promo/vendor/
sssd-devel@lists.fedorahosted.org
-
Stephen Gallagher -
Sumit Bose