[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: idletimeout (was: openldap client connect limit)

To: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Subject: Re: idletimeout (was: openldap client connect limit)
From: Jan-Piet Mens <jpm@retail-sc.com>
Date: Wed, 27 Apr 2005 10:18:23 +0200
Cc: OpenLDAP-software@OpenLDAP.org
Content-disposition: inline
In-reply-to: <hbf.20050426oegf@bombur.uio.no>
References: <002701c54a5d$e4a61230$756b460a@china.huawei.com> <873AD4E89BB1000C5649BD7C@cadabra-dsl.stanford.edu> <426E769E.1060108@symas.com> <hbf.20050426oegf@bombur.uio.no>
User-agent: Mutt/1.5.7i

On Tue Apr 26 2005 at 22:20:41 CEST, Hallvard B Furuseth wrote:

> Another wish: Ability to exempt a few IP-addresses, bound DNs etc. from
> idletimeout.  I'd like to tune our idletimeout _way_ down, but currently
> that would break our MTA.  Not a good idea:-)

I'd like to second that wish. Perhaps an addition to the `limits' option?

	| limits  dn.exact="cn=whatsit,dc=example,dc=com"
	| 	size.hard=none
	| 	idle=180

	-JP

References:
- openldap client connect limit
  - From: 罗志坚 <luozhijian@huawei.com>
- Re: openldap client connect limit
  - From: Quanah Gibson-Mount <quanah@stanford.edu>
- Re: openldap client connect limit
  - From: Howard Chu <hyc@symas.com>
- idletimeout (was: openldap client connect limit)
  - From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>

Prev by Date: Non-numeric OIDs
Next by Date: Re: OpenLDAP schema
Index(es):
- Chronological
- Thread