Date: Thu, 19 Jun 2014 14:06:56 +0200 From: Rolf Nielsen <rmg1970swe@gmail.com> To: Dewayne Geraghty <dewayne.geraghty@heuristicsystems.com.au>, Mateusz Guzik <mjguzik@gmail.com> Cc: FreeBSD Stable Mailing List <freebsd-stable@freebsd.org> Subject: Re: Unchangeable sysctl's in FreeBSD10.0 Stable Message-ID: <53A2D260.90606@gmail.com> In-Reply-To: <53A1B6C0.50701@heuristicsystems.com.au> References: <53A15911.5020507@heuristicsystems.com.au> <20140618113246.GA7157@dft-labs.eu> <53A1B6C0.50701@heuristicsystems.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 2014-06-18 17:56, Dewayne Geraghty wrote:
> On 18/06/2014 9:32 PM, Mateusz Guzik wrote:
>> On Wed, Jun 18, 2014 at 07:17:05PM +1000, Dewayne Geraghty
>> wrote:
>>> While migrating from 9.2 Stable (9.3Beta3) to 10.0Stable
>>> (r267307M) I noticed that some of the sysctl's that I adjust
>>> for tuning purposes aren't writeable, instead sysctl returns an
>>> "Invalid argument". The two sysctl's of interest are:
>>> net.flowtable.maxflows and kern.ipc.maxsockets
>>>
>>> Would someone advise the new way that these can be adjusted to
>>> suite the purpose of the servers? There was no mention in
>>> src/UPDATING.
>>>
>> EINVAL most likely comes from sysctl handler for given variable
>> if it is unhappy with new value.
>>
>> net.flowtable.maxflows's will complain if you are trying to
>> shrink it.
>>
>> kern.ipc.maxsockets's will complain if the following does not
>> hold: if (newmaxsockets > maxsockets && newmaxsockets <=
>> maxfiles) {
>>
>>
>> maxfiles can be read from kern.maxfiles
>>
> Thanks for providing feedback and advice.
>
> Mateusz, You've given me a clue and yes, I probably need to read
> the code first; I had maxsockets=maxfiles+8. The default for this
> 10.0 Stable amd64 machine, with 8GB and kern.maxusers="512" #
> sysctl -ae | egrep "maxsockets|maxfiles=" kern.maxfiles=254868
> kern.ipc.maxsockets=254870
>
> Rolf, good suggestion. Though its probably better to check, in my
> case sysctl -Ta|egrep "maxsockets|maxflows" # Checks for variables
> set within loader.conf sysctl -Wa | egrep "maxsockets|maxflows" #
> Checks for variables set via sysctl.conf (or sysctl).
>
> These particular variables are writeable via sysctl. And frankly,
> I'm pleased that sysctl did perform a sanity check and rejected my
> numbers, something that I'll need to investigate further. :)
>
> Kind regards, Dewayne.
>
>
>
>
You're probably right. My reply was just a quick reaction. I don't
fiddle with those specific sysctl's, but I do set some other ones in
loader.conf. However, those are, according to the information,
intentionally read only while in multiuser, thus required to be set early.
Rolf
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBAgAGBQJTotJgAAoJEB1OKfQ0M8TgvbEQANunEpLn6Exs80by2c+xgXB1
czzwKZLw3p+y9a1K105cJVUf0/P/gQDk8oOqECBWJw6P+EGsza1BWrpnDCyyxgLA
Nu+TIdNwghC6f2uRTb0qCPMUlMiXlXrYfvun66jhP5n/00gkzn374TEy8H6EFdnA
3cfRvn8Jtk/hvioqAsJWU9y1KOhTE9rEpPdfuPCAwsixvfG1MNub4EGSQk3uSIcQ
4vnayNP9LWuYCwMZxK2UgLS15DOvc7qMYyHUCFcmXRyljXHg4oaZ2tsdFhN+46r4
FcJIQnGHObau6giN4n80ay2i0JqcriiBwVAhR2ENwXRxLmezbPa9bu+7TDn+pEch
J4UWomYytx0CN8beanqeuXo1xf6wXgUwvx6O+UhDZpRKoOg0QOw3efaTiHh5QvHV
ZWY8P1cyxMT7g2ApukGm7/+krJ2E6ONtz0ImWEZtLqpomXFKqk3YJQkkBuoTa8Ub
76jY0fly5BeK5qlEIs4MeGLoTkQk8O67203T5ayON8DERVj0SQVnHqho6nyv+B23
tAsV8f4eqXCtAhhqLesOWK1G2tOO6xrLkQ9j3MQj1JGVm69ZQWRe8THpid/Ky0vB
Rvo+3B00a+VRTwNAZaZ7ecBzW83OuntmuuImuI14kPyTkqSLWy8YO4QHvYAqY4q3
+EfPEFZQ+0zvKqaitRyB
=RRu9
-----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?53A2D260.90606>