On 09/05/12 09:04, Ali Jawad wrote:
Hi
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 ?
what makes you think that this is a client config option? Are you
confusing it with "timelimit"?
idle_timelimit is a server option to configure for closing idle connections.
GREG
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
Regards
--
389 users mailing list
389-users@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/389-users
--
Greg Matthews 01235 778658
Scientific Computing Group Leader
Diamond Light Source Ltd. OXON UK
--
This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
--
389 users mailing list
389-users@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/389-users
