freebsd stable - Jun 2014 - Unchangeable sysctl's in FreeBSD10.0 Stable

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.

Regards, Dewayne.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2014-06-18 11:17, 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.
> 
> Regards, Dewayne.
If you set them in /etc/sysctl.conf, try setting them in
/boot/loader.conf instead.

Rolf
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBAgAGBQJToWItAAoJEB1OKfQ0M8TgqkAQANzty0wuxwQgF1/tdpP6/7vZ
n9GHlZWj+wnZlobjskPST93sAHiL8xnOkWW0YGFxvgbxQ2O07aU9oMTj/TYtjj/k
boDQhUcXx6nMWdwqv8f5c/O36VVFHJ5qFCfPhYXX5cfDgqgPmlERK4tam0ZS3XO+
5MeE/cKIe1PjKoHA2eXgpkQI7716GxV4paRGFmcTusCtYgC73Mf46hiS4WG5RsJh
sWbjI/+/zlci9S9wGlB0jE6ikDkjkq7EFlqzQJSuWk8sLyoOnXtV3WBHFbjyvAql
nQJwdko3ufo2xb8+5tYPSPID5mmsVS6fxcdikfFpAEPgwjo8NC2EsqdL2LYvO9eJ
TenJJ706QOtwtABtufnefcolsKjZ56r+Y80s4BXDJEbHIrhzZ6dgAUiwmMzfqwjm
G067IVe0wcaYTSUYxObbwnOmM7ZXxyODEpHfWyUDblsPYplFR6MJ6+a8aYwClH59
R2+7HnP3QbXbKp2VmUdoWv8jBoKm78BTtVzm4nMQ0dn1UWjUBw6G77DhCRVLfrEv
r6SMRgvlmDZqJwF6S4FIGDiCc6RpZtUqFY7ZhUzpad03DE4fVQMAYd0rzcfmH7iJ
DsZACfKjQpIVRaOOYITcwNQoEhqqt+broTUHKVF5JcMQ6ZtpNmBO55eYF6OMmAH1
Oaf2AIyyD5ShUc0e5Cwp
=Tqql
-----END PGP SIGNATURE-----

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

-- 
Mateusz Guzik <mjguzik gmail.com>