From owner-freebsd-stable@FreeBSD.ORG Thu Apr 7 20:29:57 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7342916A4CE for ; Thu, 7 Apr 2005 20:29:57 +0000 (GMT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B04743D46 for ; Thu, 7 Apr 2005 20:29:57 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id j37KTmat027608; Thu, 7 Apr 2005 13:29:48 -0700 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id j37KTmfI027607; Thu, 7 Apr 2005 13:29:48 -0700 Date: Thu, 7 Apr 2005 13:29:48 -0700 From: Brooks Davis To: bob@a1poweruser.com Message-ID: <20050407202947.GB21190@odin.ac.hmc.edu> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="TakKZr9L6Hm6aLOc" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu cc: stable@freebsd.org Subject: Re: nfsiod tasks started in error X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Apr 2005 20:29:57 -0000 --TakKZr9L6Hm6aLOc Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Apr 07, 2005 at 04:11:55PM -0400, bob@a1poweruser.com wrote: > During sysinstall answered no to the server and client nfs questions > and after installed completed and system rebooted I see task > nfsiod1,2,3,4 running in output of ps ax command. This was not the > case in any of the 4.x releases. This can be looked upon as a > security leak. This may be a error in the new boot up process. This > was first reported 1/16/2004 in 5.2 RC2 as Problem Report kern/61438 > and again in 5.3 as Problem Report kern/79539 >=20 > I tried to run /usr/local/etc/rc.d/killnfs.sh script to kill these > unwanted tasks but that does not work. >=20 > Any suggestions on how I can kill these bogus nfs tasks as part of > boot up or what to change in the boot up process so these tasks > don't get started in the first place? Doing a manual recompile of > the kernel to remove the nfs statements is not a viable solution. nfsiod now runs as a kernel process and is control by these sysctls: vfs.nfs.iodmaxidle: 120 vfs.nfs.iodmin: 4 vfs.nfs.iodmax: 20 It looks like setting vfs.nfs.iodmin=3D0 and then klling them off works. We probably should think about changing the default to 0 and setting appropriate values via /etc/rc.d/nfs. Over all, I can't say this is a very high priority though patches would certaintly be accepted. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --TakKZr9L6Hm6aLOc Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFCVZg6XY6L6fI4GtQRAt8oAJ0dPkxZcU5uy8ySVkhdzqBu8eiWIQCg59pA wWojMzqTC4EcL/mTU8ZrzDc= =VzQ/ -----END PGP SIGNATURE----- --TakKZr9L6Hm6aLOc--