[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Using back-ldap as a client-side proxy/cache

On 26 Mar 2010, at 17:14, Neil Dunbar wrote:

On 26 Mar 2010, at 08:50, masarati@aero.polimi.it wrote:

Changed the templates to lower case. All working now. Thanks, Howard.

Your temporary fix is probably fine.  Though, I'd consider this a bug: the
case should not matter.  I suggest you file an ITS.

Although I'm not quite seeing where in the code the case of that
configuration may matter.

Not sure either. The pCacheQueryURL attribute description has an MR of caseExactMatch, could that be it?

Looks like it's not a case issue after all. It seems like the results of some of my queries are being cached (ie, groups) but some aren't (ie, users).

Which results in some oddities: getent group foo (while not in cache) will correctly fetch the group details and its membership, but next time I run the command, I get the group name gid fetched from cache, but with no users. Running debug trace shows that the DNs of the members are indeed stored in cache, but it fails to fetch those DNs and their corresponding entries from cache.

Whereas getent passwd bar seems always to fetch from the backend directory (back-ldap), and not attempt to store the results in cache. Very odd indeed...

I'll keep on hacking on this one. Howard's config advanced the position considerably - I just need to work out why some of the templates don't trigger cache population.



Systems Architect

(602) 850-5783 work
+44 7976 616583 mobile
+1 (602) 535-6914 US mobile