> From:  "Sydney Bogaert" <[EMAIL PROTECTED]>
> Date:  Wed, 29 Aug 2007 17:40:33 +0200
>
> Did you try to set the timeout in the configuration files ?
> echo -n 600 > config/timeout 
> By default it is set to 1200 seconds (20 minutes).

I've got 120 in /var/qmail/control/timeoutsmtpd; based on the below code, that 
should work.

> See in lib/Qpsmtpd/TcpServer.pm :
> 
> sub read_input {
>   my $self = shift;
> 
>   my $timeout =
>     $self->config('timeoutsmtpd')   # qmail smtpd control file
>       || $self->config('timeout')   # qpsmtpd control file
>         || 1200;                    # default value
> 
>   alarm $timeout;
>   while (<STDIN>) {
>     alarm 0;
>     $_ =~ s/\r?\n$//s; # advanced chomp
>     $self->log(LOGINFO, "dispatching $_");
>     $self->connection->notes('original_string', $_);
>     defined $self->dispatch(split / +/, $_, 2)
>       or $self->respond(502, "command unrecognized: '$_'");
>     alarm $timeout;
>   }
>   alarm(0);
> }
> 
> If you have connections running for more than one hour, the client must
> be saying something during this time.
> You can try to lower the timeout parameter.  Mine is 120s (maybe a
> little short, but it works quite well).
> 
> 
> Sydney.

-- 
Chris Garrigues                         Trinsic Solutions
President                               710-B West 14th Street
                                        Austin, TX  78701-1798
http://www.trinsics.com/blog
http://www.trinsics.com                 512-322-0180

                 Would you rather proactively pay for
                uptime or reactively pay for downtime?

                          Trinsic Solutions
                Your Trusted Friends in Proactive IT.


Attachment: pgpdVfOKIDksj.pgp
Description: PGP signature

Reply via email to