From owner-freebsd-isp@FreeBSD.ORG Wed Jan 4 19:09:07 2006 Return-Path: X-Original-To: freebsd-isp@freebsd.org Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3038816A41F for ; Wed, 4 Jan 2006 19:09:07 +0000 (GMT) (envelope-from lists@stringsutils.com) Received: from zoraida.natserv.net (p65-147.acedsl.com [66.114.65.147]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2C67843D55 for ; Wed, 4 Jan 2006 19:09:05 +0000 (GMT) (envelope-from lists@stringsutils.com) Received: from zoraida.natserv.net (zoraida.natserv.net [66.114.65.147]) by zoraida.natserv.net (Postfix) with ESMTP id 4DDF77D8C; Wed, 4 Jan 2006 14:09:04 -0500 (EST) References: <17339.61532.649959.1059@canoe.dclg.ca> Message-ID: X-Mailer: http://www.courier-mta.org/cone/ From: Francisco Reyes To: David Gilbert Date: Wed, 04 Jan 2006 14:09:04 -0500 Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="US-ASCII" Content-Disposition: inline Content-Transfer-Encoding: 7bit Cc: FreeBSD ISP Subject: Re: FreeBSD +NFS + mail services X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2006 19:09:07 -0000 David Gilbert writes: > remaining processes have little or none. As more of your NFS > processes are charged for time, you may want to increase the number > you run. FreeBSD seems to run more client daemons dynamically, so you > only need to worry about the number of server daemons you run. I have the following on a machine: ps aux|head -n 1|ps auxw |grep nfs root 317 0.0 0.0 0 8 ?? DL 12:47PM 0:00.41 [nfsiod 0] root 318 0.0 0.0 0 8 ?? DL 12:47PM 0:00.31 [nfsiod 1] root 319 0.0 0.0 0 8 ?? DL 12:47PM 0:00.19 [nfsiod 2] root 320 0.0 0.0 0 8 ?? DL 12:47PM 0:00.12 [nfsiod 3] root 2316 0.0 0.0 0 8 ?? DL 1:17PM 0:00.06 [nfsiod 4] root 2317 0.0 0.0 0 8 ?? DL 1:17PM 0:00.04 [nfsiod 5] root 5486 0.0 0.0 0 8 ?? SL 1:39PM 0:00.02 [nfsiod 6] root 5637 0.0 0.0 0 8 ?? SL 1:39PM 0:00.01 [nfsiod 7] root 5638 0.0 0.0 0 8 ?? SL 1:39PM 0:00.01 [nfsiod 8] root 6563 0.0 0.0 0 8 ?? SL 1:46PM 0:00.01 [nfsiod 9] root 6564 0.0 0.0 0 8 ?? SL 1:46PM 0:00.00 [nfsiod 10] root 6565 0.0 0.0 0 8 ?? IL 1:46PM 0:00.00 [nfsiod 11] root 6566 0.0 0.0 0 8 ?? IL 1:46PM 0:00.00 [nfsiod 12] root 6567 0.0 0.0 0 8 ?? IL 1:46PM 0:00.00 [nfsiod 13] root 7089 0.0 0.0 0 8 ?? IL 1:51PM 0:00.00 [nfsiod 14] root 7090 0.0 0.0 0 8 ?? IL 1:51PM 0:00.00 [nfsiod 15] root 7091 0.0 0.0 0 8 ?? IL 1:51PM 0:00.00 [nfsiod 16] root 7092 0.0 0.0 0 8 ?? IL 1:51PM 0:00.00 [nfsiod 17] root 7093 0.0 0.0 0 8 ?? IL 1:51PM 0:00.00 [nfsiod 18] root 7095 0.0 0.0 0 8 ?? IL 1:51PM 0:00.00 [nfsiod 19] It seems that for the most part most of those nfs clients are not used. I then wonder why they were started. What would be the impact on setting the upper limit of clients to 10? Specially on a case like the above it doesn't seem like 20 were needed to begin with.. Also, on the server how does one change the number of running server daemons? Only way I found was to kill all nfsd daemons and start it with the new number of clients.. there must be a better way (I sure hope so).