Added an alarm around the search call (using
Sys::SigAction) and the problem persisted.
Did some further debugging and the hang actually
occurs around ldap_error_text call after checking
$mesg-code.
Surprisingly this call was actually within the bounds
of the alarm (I only set alarm(0) after).
H
Thanks for that information Chris.
Problem is that I have the same problem with my mysql
dbi connection and I'm not sure if I can get the
socket connect handle there. I'll dig further.
--- Chris Ridd <[EMAIL PROTECTED]> wrote:
> On 17/3/05 11:13 pm, Chris Masters
> <[EMAIL PROTECTED]> wrote:
>
>
On 17/3/05 11:13 pm, Chris Masters <[EMAIL PROTECTED]> wrote:
> Thanks Chris, that looks much simpler than an external
> timeout mechanism.
Only if it fools your firewall ;-)
> The default timeout for SO_KEEPALIVE seems to be 2
> hours. Any ideas how I can change this to 30 mins for
> example?
Thanks Chris, that looks much simpler than an external
timeout mechanism.
The default timeout for SO_KEEPALIVE seems to be 2
hours. Any ideas how I can change this to 30 mins for
example?
--- Chris Ridd <[EMAIL PROTECTED]> wrote:
> On 17/3/05 9:03 pm, Chris Masters
> <[EMAIL PROTECTED]> wrote:
>
On 17/3/05 9:03 pm, Chris Masters <[EMAIL PROTECTED]> wrote:
> Hi All,
>
> A pesky firewall is closing connections silently after
> a period of inactivity. When my client calls search it
> hangs.
>
> What's the best way to place a timeout on the search
> call? In C, I would use an alarm signal o
Hi All,
A pesky firewall is closing connections silently after
a period of inactivity. When my client calls search it
hangs.
What's the best way to place a timeout on the search
call? In C, I would use an alarm signal or select(2).
Thanks for any help on this.
Chris
_
