Re: (ITS#4160) idletimeout configuration directive being processed late

[hyc@symas.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.

quanah@stanford.edu wrote:
> Full_Name: Quanah Gibson-Mount
> Version: REL ENG 2-3
> OS: Solaris 8
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (171.64.19.82)
>
>
> In looking at the logs of my REL ENG 2.3 build from 11/4/2005, I find that
> idletimeouts are not being processed when requested, with a noticeable lag in
> place.  2.2 was much more diligent about closing them near the idletimeout mark
> (within 2 seconds)
>
> Examples:
>
> Nov  7 14:59:47 ldap9.Stanford.EDU slapd[9764]: [ID 167594 local4.debug]
> conn=19914 op=1 SEARCH RESULT tag=101 err=0 nentries=1 text=
> Nov  7 15:00:24 ldap9.Stanford.EDU slapd[9764]: [ID 485650 local4.debug]
> conn=19914 fd=75 closed (idletimeout)
>
> Nov  7 15:03:14 ldap9.Stanford.EDU slapd[9764]: [ID 167594 local4.debug]
> conn=19925 op=1 SEARCH RESULT tag=101 err=0 nentries=1 text=
> Nov  7 15:03:49 ldap9.Stanford.EDU slapd[9764]: [ID 485650 local4.debug]
> conn=19925 fd=75 closed (idletimeout)
>
> Nov  7 15:01:32 ldap9.Stanford.EDU slapd[9764]: [ID 167594 local4.debug]
> conn=19921 op=1 SEARCH RESULT tag=101 err=0 nentries=1 text=
> Nov  7 15:02:13 ldap9.Stanford.EDU slapd[9764]: [ID 485650 local4.debug]
> conn=19921 fd=75 closed (idletimeout)
>
>
>
>
>
>
>   


-- 
  -- Howard Chu
  Chief Architect, Symas Corp.  http://www.symas.com
  Director, Highland Sun        http://highlandsun.com/hyc
  OpenLDAP Core Team            http://www.openldap.org/project/