From owner-freebsd-questions@FreeBSD.ORG Tue Jan 23 22:19:15 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C2CFF16A402 for ; Tue, 23 Jan 2007 22:19:15 +0000 (UTC) (envelope-from zbyszek@szalbot.homedns.org) Received: from lists.lc-words.com (lists.lc-words.com [83.19.156.210]) by mx1.freebsd.org (Postfix) with ESMTP id 73ECC13C4C2 for ; Tue, 23 Jan 2007 22:19:15 +0000 (UTC) (envelope-from zbyszek@szalbot.homedns.org) Received: from localhost.168.11.51 ([::1] helo=lists.lc-words.com) by lists.lc-words.com with esmtp (Exim 4.66 (FreeBSD)) (envelope-from ) id 1H9Tzo-00058E-1d for freebsd-questions@freebsd.org; Tue, 23 Jan 2007 23:20:04 +0100 Received: from 192.168.11.7 (SquirrelMail authenticated user zbyszek@szalbot.homedns.org) by lists.lc-words.com with HTTP; Tue, 23 Jan 2007 23:20:04 +0100 (CET) Message-ID: <62343.192.168.11.7.1169590804.squirrel@lists.lc-words.com> In-Reply-To: <45B68887.3070105@placidpublishing.net> References: <45B4032C.3070404@placidpublishing.net> <45B5295D.3020205@placidpublishing.net> <45B68887.3070105@placidpublishing.net> Date: Tue, 23 Jan 2007 23:20:04 +0100 (CET) From: "Zbigniew Szalbot" To: freebsd-questions@freebsd.org User-Agent: SquirrelMail/1.4.9a MIME-Version: 1.0 Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Subject: Re: rsync issues 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, 23 Jan 2007 22:19:15 -0000 Hi, > I've gotten a few replies and i've tried almost all of the suggestions > but the problem still resides. I re-installed rsync on both box's and it > still does this. Most likely won't help, but do you have any sort of traffic shaping between the two boxes (not sure if they are on the same LAN or remote), but it is something to check - give appropriate bandwidth for the operation. If they are remotely localted, how about trying to rsync locally (picking up a similar machine) and see if you get the same error. I am not a technical guy. I am just suggesting to check QoS. Warm regards, -- Zbigniew Szalbot