From owner-freebsd-stable@FreeBSD.ORG Wed Jun 18 11:32:52 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AC5E4EC9 for ; Wed, 18 Jun 2014 11:32:52 +0000 (UTC) Received: from mail-wg0-x229.google.com (mail-wg0-x229.google.com [IPv6:2a00:1450:400c:c00::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 401882683 for ; Wed, 18 Jun 2014 11:32:52 +0000 (UTC) Received: by mail-wg0-f41.google.com with SMTP id a1so679207wgh.0 for ; Wed, 18 Jun 2014 04:32:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=87bdcNxou25IHktcOUpDjUexVefeGrC3FiPwqjALOpo=; b=KYVxZLMlXAsGcvv9oaiDI9y8kz9CvaezzNV7jSMSGSQH0iLmUXM1+VIy7qdBCxUfNq ErMoDZNZFcRQGJngqf+oZwleKvLCxUvmwhT9zPPIK4MooVqFN1s84hKIPReT8tvFdRCg GjG2W73bkWsVjWsPvRBfsarlaVGmXl384Le7hjOWFA7HFniQrvm+DqHMLiJu/pO36nfw Mw756v2IkBozUwNm8+4rMfCyGpn2GWs4pp4cg3dYtJKM2LbYzwqPcsbQ3wgF30aVCxhy dpa9N+2Jp3yWX/SaVNMP+EfH80/aIJ6uuxeetyL2p3Qp3wrLouillUQqCrlbyHHAvg8C oU3A== X-Received: by 10.180.99.99 with SMTP id ep3mr4559313wib.42.1403091170350; Wed, 18 Jun 2014 04:32:50 -0700 (PDT) Received: from dft-labs.eu (n1x0n-1-pt.tunnel.tserv5.lon1.ipv6.he.net. [2001:470:1f08:1f7::2]) by mx.google.com with ESMTPSA id bq7sm25159193wib.7.2014.06.18.04.32.48 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Wed, 18 Jun 2014 04:32:49 -0700 (PDT) Date: Wed, 18 Jun 2014 13:32:47 +0200 From: Mateusz Guzik To: Dewayne Geraghty Subject: Re: Unchangeable sysctl's in FreeBSD10.0 Stable Message-ID: <20140618113246.GA7157@dft-labs.eu> References: <53A15911.5020507@heuristicsystems.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <53A15911.5020507@heuristicsystems.com.au> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: FreeBSD Stable Mailing List X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Jun 2014 11:32:52 -0000 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