<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'><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>
<P id=SkyDrivePlaceholder> </P>
<BR>
> Subject: Re: [SSSD] SSSD netgroup issue<BR>> From: sgallagh@redhat.com<BR>> To: sssd-devel@lists.fedorahosted.org<BR>> CC: <A 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></body>
</html>