On Tue, 12 Apr 2011 12:54:54 -0400
Stephen Gallagher <sgallagh(a)redhat.com> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Now that gecos can come from either the 'gecos' or 'cn' attributes,
we need to ensure that we never remove it from the cache.
We were being too greedy with our removal code. It purges from the
sysdb cache any attributes that were requested from LDAP but that we
did not get. However, in the case of 'gecos' (if we are falling back
to 'cn') this would mean that we were always purging the
gecos-from-cn value.
I am actually wondering why we are storing a duplicate here instead of
retrieving CN in the nss responder and substituting the gecos field
there, it would waste less space for a perfectly duplicate attribute
and would avoid update corner cases like this one.
Simo.
--
Simo Sorce * Red Hat, Inc * New York