Thanks Guys, I figured this one out, my other post about force change password on reset is killing me though.

On Wed, May 9, 2012 at 4:22 PM, Paul Robert Marino <> wrote:

Its gennerally a goot idea on the server to set a shorter tcp keepalive interval in /etc/sysctl.conf
The default is 2 hours. Set it to slightly more than the idle time limit on your clients.

On May 9, 2012 4:05 AM, "Ali Jawad" <> wrote:
I know this is not a strictly 389 DS related question. I did set idle_timelimit 60 in my /etc/ldap.conf client file but connections stay running and do not time out. Is there any setting I need to add on the server side ?

My Full Ldap file at /etc/ldap.conf

bind_policy soft
URI ldap://xx.xx.xx.xx
BASE dc=xxxxxxx,dc=local
TLS_CACERTDIR /etc/openldap/cacerts
pam_password clear
pam_lookup_policy yes

idle_timelimit 60


389 users mailing list

Ali Jawad
Information Systems Manager
Splendor Telecom (
Beirut, Lebanon
Phone: +9611373725/ext 116
FAX: +9611375554