if you use an openldap version which doesn't support this on linux, you should modify the systems parameters :
/proc/sys/net/ipv4/tcp_keepalive_intvl /proc/sys/net/ipv4/tcp_keepalive_probes /proc/sys/net/ipv4/tcp_keepalive_time
Regards,
Olivier
________________________________________ De : openldap-technical-bounces@OpenLDAP.org [openldap-technical-bounces@OpenLDAP.org] de la part de Quanah Gibson-Mount [quanah@zimbra.com] Date d'envoi : jeudi 12 janvier 2012 19:01 À : Aaron Richton; ZHOU Eric JP Cc : ANTHONY Michael; qdlcp-security@list.alcatel-lucent.com; HO Yao; VAN RANGELROOIJ Ardo; openldap-technical@openldap.org Objet : RE: OpenLDAP replciation issue with MirrorMode
--On Thursday, January 12, 2012 9:14 AM -0500 Aaron Richton richton@nbcs.rutgers.edu wrote:
Actually, I'm starting to wonder if this should be an option you can pass as a syncrepl (really libldap) configuration directive. There's something to be said for having aggressive-ish keepalives on server-to-server communication (with, hopefully, good bandwidth/latency/communication costs/etc.) and keeping your site defaults for "normal" clients. OpenLDAP already inched in this direction with the ability to set different idletimeout, etc., for the syncrepl client. Is anybody interested in this? Maybe I'll do it (or have a student do it) if a few people think it'd help...
I'm guessing you haven't read the syncrepl section of the man pages in a while. See the "keepalive" option.
--Quanah
--
Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration