From owner-freebsd-stable@FreeBSD.ORG Thu Apr 7 20:36:27 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 DE5A816A4CE for ; Thu, 7 Apr 2005 20:36:27 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.111]) by mx1.FreeBSD.org (Postfix) with ESMTP id 985B143D48 for ; Thu, 7 Apr 2005 20:36:27 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 055AE514D6; Thu, 7 Apr 2005 13:36:26 -0700 (PDT) Date: Thu, 7 Apr 2005 13:36:26 -0700 From: Kris Kennaway To: Brooks Davis Message-ID: <20050407203626.GB33137@xor.obsecurity.org> References: <20050407202947.GB21190@odin.ac.hmc.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="GID0FwUMdk1T2AWN" Content-Disposition: inline In-Reply-To: <20050407202947.GB21190@odin.ac.hmc.edu> User-Agent: Mutt/1.4.2.1i 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:36:28 -0000 --GID0FwUMdk1T2AWN Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Apr 07, 2005 at 01:29:48PM -0700, Brooks Davis wrote: > 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. >=20 > nfsiod now runs as a kernel process and is control by these sysctls: >=20 > vfs.nfs.iodmaxidle: 120 > vfs.nfs.iodmin: 4 > vfs.nfs.iodmax: 20 >=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. This was a deliberate change by Peter, since if you have NFSCLIENT in the kernel it's assumed you want to use the machine as a NFS client. Kris --GID0FwUMdk1T2AWN Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCVZnKWry0BWjoQKURAkoPAJ9Z3AUxg9Di+GVsWbloagDHZBM6MwCfahQt XXlsiiBz0p3PyOaizTgKkmY= =D3Y0 -----END PGP SIGNATURE----- --GID0FwUMdk1T2AWN--