Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 23 Jul 2000 16:23:46 -0700 (PDT)
From:      Kelly Yancey <kbyanc@posi.net>
To:        Alfred Perlstein <bright@wintelcom.net>
Cc:        hackers@FreeBSD.ORG, wollman@FreeBSD.ORG
Subject:   Re: kern.ipc.maxsockbuf vs reality?
Message-ID:  <Pine.BSF.4.21.0007231620310.37411-100000@gateway.posi.net>
In-Reply-To: <20000723153345.P13979@fw.wintelcom.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 23 Jul 2000, Alfred Perlstein wrote:

> Also, if sb_max is to remain a read/write sysctl we'll need to cap
> it so that kern.ipc.maxsockbuf is always true and we don't allow
> sysadmins to shoot thier feet by scaling it too high or low, the
> only problem is that I can't for the life of me figure out the
> magic to keep sb_max (kern.ipc.maxsockbuf) as a ulong (which it
> should be, instead of an int) as well as provide a filtering
> function.
> 

  You'de have to use SYSCTL_PROC with a fmt of "LU". Just let the handler do
the sanity checking on sysctl writes.

  Kelly

--
Kelly Yancey  -  kbyanc@posi.net  -  Belmont, CA
System Administrator, eGroups.com                  http://www.egroups.com/
Maintainer, BSD Driver Database       http://www.posi.net/freebsd/drivers/
Coordinator, Team FreeBSD        http://www.posi.net/freebsd/Team-FreeBSD/



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0007231620310.37411-100000>