Matt Sergeant wrote:
>
> I'm thinking more on the lines of pushing back reads if they're not full
> lines.
>
> Probably needs a bit of support for that in lib/Danga/Client.pm
Attached is an attempt to do that. The reason for this is that I've seen
another case of end of data marker coming in t
Hi,
I've been able to get the problem down to a minimum (I think). It has
been a quite arduous work... And I assure you that the machines that
were "hanging" the connections where doing VERY STRANGE THINGS :S
The client seemed to be cutting the connection just after the DATA
command (as the
Charlie Brady escribió:
This is where I pop up and remind folks there's a long-standing bug that
no time limits are applied to plug-in callbacks.
Right now I don't know if plugin callbacks would solve this problem. I'm
starting to think it is DESTROY related... I feel that plugin timeouts
ar
On Wed, 23 Apr 2008 20:32:39 +0200
Jose Luis Martinez <[EMAIL PROTECTED]> wrote:
> I've been bugging aroung the Qp code to find what's going on with these
> processes... What was my surprise when I saw:
>
> $SIG{ALRM} = sub {
> print $client "421 Connection Timed Out\n";
> ::
