From owner-freebsd-questions@FreeBSD.ORG Tue Jul 4 04:01:40 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 532A616A4E1 for ; Tue, 4 Jul 2006 04:01:40 +0000 (UTC) (envelope-from scuba@centroin.com.br) Received: from trex.centroin.com.br (trex.centroin.com.br [200.225.63.134]) by mx1.FreeBSD.org (Postfix) with ESMTP id B5EDF43D45 for ; Tue, 4 Jul 2006 04:01:39 +0000 (GMT) (envelope-from scuba@centroin.com.br) Received: from trex.centroin.com.br (trex.centroin.com.br [200.225.63.134]) by trex.centroin.com.br (8.13.4/8.13.3) with ESMTP id k6441xe3061633 for ; Tue, 4 Jul 2006 01:01:59 -0300 (BRT) (envelope-from scuba@centroin.com.br) Date: Tue, 4 Jul 2006 01:01:59 -0300 (BRT) From: scuba@centroin.com.br Sender: mpsouza@trex.centroin.com.br To: freebsd-questions@freebsd.org Message-ID: <20060704004255.Q42828@trex.centroin.com.br> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: TCP timeout X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Jul 2006 04:01:40 -0000 Hi folks, I'm facing some troubles with mail server on a busy slow link. I'm getting a lot of "sendmail: SYSERR: collect: read timeout on connection from" entries in the logs. I found this page showing an workaround for Solaris. Is it applicable for Free BSD 5.4? If positive, is there any sysctl variable to tun it? -----------------xxxxxx----------------- TCP/IP connections time out too soon, especially on slow links. The tcp/ip abort interval in Solaris 2.x is too short, the default value is 2 minutes. The result is that when an ACK isn't received in 2 minutes, the connection is closed. This is most often seen by sendmail, which will log sendmail: SYSERR: collect: read timeout on connection from ... You can fix this by running following command which increases the timeout to 8 minutes (unit is millisec), which is the Solaris 2.4+ (and patched 2.3) default. /usr/sbin/ndd -set /dev/tcp tcp_ip_abort_interval 480000 -----------------xxxxxx----------------- - Marcelo