<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
On 09/23/2011 05:55 PM, Francisco Javier Marín Murillo wrote:
<blockquote cite="mid:SNT112-W6420E0799F237514967509FE0F0@phx.gbl"
type="cite">
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
<div dir="ltr">
Thank you Stephen. But I set entry_cache_timeout to 90
seconds. The issue is that even setting it to 90 seconds or 5
seconds it never times out(even after 90 seconds or 5 seconds is
expired). It never ever expires. I have checked the client the
next day and the entry is still in the database That is the
issue. What can be causing this ? is it something wrong with
the sssd service that does not read correctly the sssd.conf
configurations ?<br>
</div>
</blockquote>
<br>
<br>
Might be a bug...<br>
Stephen it is worth inspecting the code where we check the
expiration timeout may be we do something wrong there.<br>
<br>
<blockquote cite="mid:SNT112-W6420E0799F237514967509FE0F0@phx.gbl"
type="cite">
<div dir="ltr">
<p id="SkyDrivePlaceholder"> </p>
<br>
> Subject: Re: [SSSD] SSSD netgroup issue<br>
> From: <a class="moz-txt-link-abbreviated" href="mailto:sgallagh@redhat.com">sgallagh@redhat.com</a><br>
> To: <a class="moz-txt-link-abbreviated" href="mailto:sssd-devel@lists.fedorahosted.org">sssd-devel@lists.fedorahosted.org</a><br>
> CC: <a moz-do-not-send="true"
href="mailto:chisco.13@hotmail.com">chisco.13@hotmail.com</a><br>
> Date: Fri, 23 Sep 2011 15:09:40 -0400<br>
> <br>
> On Fri, 2011-09-23 at 13:00 -0600, Francisco Javier Marín
Murillo wrote:<br>
> > Just to let you know the only way how I have been able
to expire<br>
> > netgroup cache is when I delete db cache and restart
sssd. But that<br>
> > does not work for us because we want sssd to expire
cache<br>
> > automatically with no manual intervention.<br>
> > <br>
> <br>
> As I wrote in my other email, there will always be a lag,
based on the<br>
> entry_cache_timeout value. This is to reduce the load on
your LDAP<br>
> server, under the reasonable expectation that entries in
LDAP are<br>
> "write-rarely, read often". In the majority of cases, you
don't want to<br>
> waste time and CPU on constantly going out the LDAP server.<br>
> <br>
> For the reverse, there's no way for the LDAP server to
"push" updates to<br>
> the clients. LDAP doesn't work that way. All data requests
have to<br>
> originate with the clients. So there's no way to achieve an<br>
> instantaneous update when something changes.<br>
> <br>
<br>
</div>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
sssd-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:sssd-devel@lists.fedorahosted.org">sssd-devel@lists.fedorahosted.org</a>
<a class="moz-txt-link-freetext" href="https://fedorahosted.org/mailman/listinfo/sssd-devel">https://fedorahosted.org/mailman/listinfo/sssd-devel</a>
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Thank you,
Dmitri Pal
Sr. Engineering Manager IPA project,
Red Hat Inc.
-------------------------------
Looking to carve out IT costs?
<a class="moz-txt-link-abbreviated" href="http://www.redhat.com/carveoutcosts/">www.redhat.com/carveoutcosts/</a>
</pre>
</body>
</html>