From owner-freebsd-ports Sat Apr 14 6: 0:43 2001 Delivered-To: freebsd-ports@freebsd.org Received: from ringworld.nanolink.com (ringworld.nanolink.com [195.24.48.13]) by hub.freebsd.org (Postfix) with SMTP id 67E2E37B443 for ; Sat, 14 Apr 2001 06:00:41 -0700 (PDT) (envelope-from roam@ringworld.nanolink.com) Received: (qmail 8555 invoked by uid 1000); 14 Apr 2001 11:59:13 -0000 Date: Sat, 14 Apr 2001 14:59:13 +0300 From: Peter Pentchev To: Christopher Hall Cc: ports@FreeBSD.ORG Subject: Re: Problem with rsync Message-ID: <20010414145913.F5504@ringworld.oblivion.bg> Mail-Followup-To: Christopher Hall , ports@FreeBSD.ORG References: <200103261008.f2QA8X474965@w40.tucheng.generalresources.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200103261008.f2QA8X474965@w40.tucheng.generalresources.com>; from hsw@acm.org on Mon, Mar 26, 2001 at 06:08:32PM +0800 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Mar 26, 2001 at 06:08:32PM +0800, Christopher Hall wrote: [snip] > > D. Has anyone else seen this kind of problem or can suggest how I might > narrow down where the faults lie. Has this problem been fixed by the non-blocking IO patches that David O'Brien committed to the rsync port recently? G'luck, Peter -- Nostalgia ain't what it used to be. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message