Date: Thu, 23 Sep 2010 19:47:42 +0400 From: Ruslan Mahmatkhanov <cvs-src@yandex.ru> To: Karl Pielorz <kpielorz_lst@tdx.co.uk> Cc: freebsd-ports@freebsd.org Subject: Re: 'mbuffer' broken for network support / pipes under 7.2-R / 8.1-R? Message-ID: <4C9B769E.2080603@yandex.ru> In-Reply-To: <F766D219E8A6859B1F507A76@HexaDeca64.dmpriest.net.uk> References: <B266E3BF267EA77C5E099324@HexaDeca64.dmpriest.net.uk> <4C9A44A3.5000502@yandex.ru> <498B06B4701B41C283B7A5BF@HexaDeca64.dmpriest.net.uk> <65031285246145@web49.yandex.ru> <F766D219E8A6859B1F507A76@HexaDeca64.dmpriest.net.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
23.09.2010 18:00, Karl Pielorz пишет: > > > --On 23 September 2010 16:49 +0400 Ruslan Mahmatkhanov > <cvs-src@yandex.ru> wrote: > >> Hi Karl, >> sorry about webmail formatting. > > Yeah, it certainly mangled the original mail when quoting it! <g> > >> Try to add this line into port's Makefile, and then reinstall mbuffer: >> CFLAGS+=-m64 >> >> See if your 'network i/o' test case now passes. > > Makes no difference - it *doesn't fail* for network I/O (it completes > fine) - it just dumps a single line to stderr at the start, which says: > > " > mbuffer: warning: unable to set socket buffer size: No buffer space > available > " > > Adding '-m64' didn't get rid of that, or any of the compile time > warnings... > > I can live with the warning (better than it not working at all! :) - > unless it might be doing something nasty (like messing up network > performance - though it seems to be getting close to wire speed for > transfers). > > -Karl Ok. So i've create this PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/150885 If anybody have a clue about warnings: on build time: mbuffer.c:64:3: warning: #warning sendfile is unable to send from buffers and on run time: warning: unable to set socket buffer size: No buffer space available please add to PR. -- Regards, Ruslan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C9B769E.2080603>