From owner-freebsd-questions@FreeBSD.ORG Tue Nov 29 01:36:11 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 77F731065676 for ; Tue, 29 Nov 2011 01:36:11 +0000 (UTC) (envelope-from hg@queue.to) Received: from pickle.queue.to (pickle.queue.to [71.180.69.18]) by mx1.freebsd.org (Postfix) with ESMTP id 19E3E8FC1B for ; Tue, 29 Nov 2011 01:36:10 +0000 (UTC) Received: (qmail 38623 invoked from network); 28 Nov 2011 20:36:10 -0500 Received: from cally.queue.to (172.16.0.6) by pickle.queue.to with ESMTP; 28 Nov 2011 20:36:10 -0500 Message-ID: <4ED4370A.3090601@queue.to> Date: Mon, 28 Nov 2011 20:36:10 -0500 From: Howard Goldstein User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:8.0) Gecko/20111108 Thunderbird/8.0 MIME-Version: 1.0 To: MTaylor@bytecraft.com.au References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: too many open files X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Nov 2011 01:36:11 -0000 On 11/28/2011 19:07, Murray Taylor wrote: > > My /etc/gamin/gaminrc contains this > > fsset ufs none > fsset msdosfs none > (zfs and nfs too, if appropriate) > > and I still have 16564 files associated with gam_server in fstat out > of 17424 open files reported by sysctl kern.openfiles > > It appears that gam_server doesn't play nice with kill -HUP ( there are > 6 processes running) > and also doesn't play nice with x-org/KDE as I can often > get a program hang/crash as the kernel bitches about too many open files > Kmail is particularly susceptible to this. > > What actually initiates it as there appears to be no related entry > in either /etc/rc.d or /usr/local/etc/rc.d ? > > Currently, it is a waste of space to me, and a cause of program > instability! pkg_info -R gamin\* should lead you to an ICBM coordinates suitable for nuking and ridding yourself of the thing. I had the opposite problem where I have production box on a desktop that wants to keep monitoring (we use nautilus) but gamin_server out of the box chews up a lot of processor time (the fix for this was kernel notification for my ufs and zfs)