From owner-freebsd-ports@FreeBSD.ORG Thu Sep 23 11:40:43 2010 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2861F106566B for ; Thu, 23 Sep 2010 11:40:43 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from mail.tdx.com (mail.tdx.com [62.13.128.18]) by mx1.freebsd.org (Postfix) with ESMTP id BBFB58FC12 for ; Thu, 23 Sep 2010 11:40:42 +0000 (UTC) Received: from HexaDeca64.dmpriest.net.uk (HPQuadro64.dmpriest.net.uk [62.13.130.30]) (authenticated bits=0) by mail.tdx.com (8.14.3/8.14.3/Kp) with ESMTP id o8NBefGw003224 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO); Thu, 23 Sep 2010 12:40:41 +0100 (BST) Date: Thu, 23 Sep 2010 12:40:10 +0100 From: Karl Pielorz To: Ruslan Mahmatkhanov Message-ID: <498B06B4701B41C283B7A5BF@HexaDeca64.dmpriest.net.uk> In-Reply-To: <4C9A44A3.5000502@yandex.ru> References: <4C9A44A3.5000502@yandex.ru> X-Mailer: Mulberry/4.0.8 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Cc: freebsd-ports@FreeBSD.org Subject: Re: 'mbuffer' broken for network support / pipes under 7.2-R / 8.1-R? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Sep 2010 11:40:43 -0000 --On 22 September 2010 22:02 +0400 Ruslan Mahmatkhanov =20 wrote: > 22.09.2010 18:06, Karl Pielorz =D0=BF=D0=B8=D1=88=D0=B5=D1=82: > > Please use patch attached. It updates mbuffer to latest version that has > many 64-bit related fixes. Tell if it's now ok for you. > > -- > Regards, > Ruslan Hi, The patch/updated version seems to work fine - there's a couple of compile=20 time warnings, and when you run it using 'network' I/O you still get: " mbuffer: warning: unable to set socket buffer size: No buffer space=20 available " But it does appear to work - network mode works, and when using another=20 transport (such as 'nc' or 'ssh') as part of a pipe chain, it does=20 correctly terminate when the send is finished. Thanks! -Karl