Date: Sat, 1 Mar 2003 15:41:18 +0200
From: Ruslan Ermilov <ru@freebsd.org>
To: Garrett Wollman <wollman@lcs.mit.edu>
Cc: Alexey Zelkin <phantom@FreeBSD.org.ua>, freebsd-net@freebsd.org
Subject: Re: maxsockbuf is useless value {?|:-(}
Message-ID: <20030301134118.GE77007@sunbay.com>
In-Reply-To: <200302281931.h1SJVAUg060319@khavrinen.lcs.mit.edu>
References: <20030228130621.A16504@phantom.cris.net> <200302281931.h1SJVAUg060319@khavrinen.lcs.mit.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --]
On Fri, Feb 28, 2003 at 02:31:10PM -0500, Garrett Wollman wrote:
> <<On Fri, 28 Feb 2003 13:06:21 +0200, Alexey Zelkin <phantom@FreeBSD.org.ua> said:
>
> > Working with Sun JDK network code I have realized a need to provide some
> > range checking wrapper for setsockopt() in SO_{SND,RCV}BUF cases. Short
> > walk over documentation shown that maximum buffer size is exported via
> > kern.ipc.maxsockbuf sysctl. But attempt to use this value as maximum
> > buffer size was not successful -- it is too large for kernel.
>
> It is not intended that you do this.
>
So we can just rip it? :-)
Seriously, you didn't give any alternative. How does one
knows the maximum allowed limit? By just blindly trying?
Cheers,
--
Ruslan Ermilov Sysadmin and DBA,
ru@sunbay.com Sunbay Software AG,
ru@FreeBSD.org FreeBSD committer,
+380.652.512.251 Simferopol, Ukraine
http://www.FreeBSD.org The Power To Serve
http://www.oracle.com Enabling The Information Age
[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (FreeBSD)
iD8DBQE+YLh9Ukv4P6juNwoRAi2AAJ4+XDMLIsj+DMBrtll7j7uu3oGrAwCaAjAM
D9y9V1rVgZvM9JgQD2Q4bw8=
=qOzP
-----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030301134118.GE77007>