[Date Prev][Date Next]
Re: (ITS#4160) idletimeout configuration directive being processed late
--On Tuesday, November 08, 2005 1:25 AM -0800 Howard Chu <email@example.com>
> I think this is more to do with server load than anything else. Note that
> in the absence of other activity the server only checks once every
> (idletime/4) seconds for idle connections. So given a 30 second
> idletimeout a lag of up to 7.5 seconds would be normal. The 41 second
> interval there (11 second lag) does seem a bit abnormal, but the 37 and
> 35 second intervals are fine.
I dunno... Even on an extremely idle system at 4 in the morning I see:
Nov 8 04:21:44 ldap9.Stanford.EDU slapd: [ID 588225 local4.debug]
conn=2297 op=0 RESULT tag=97 err=0 text=
Nov 8 04:22:22 ldap9.Stanford.EDU slapd: [ID 485650 local4.debug]
conn=2297 fd=80 closed (idletimeout)
Although I suppose that is close to:
44+30 = :14 +7.5 (probably rounded to 8) = :22.
Is it perhaps doing (idletime + (idletime/4)) seconds?
Packaged, certified, and supported LDAP solutions powered by OpenLDAP: