From owner-freebsd-stable Tue Feb 29 7:51:55 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uunet.ca (mail2.uunet.ca [142.77.1.15]) by hub.freebsd.org (Postfix) with ESMTP id 61AE337BB94 for ; Tue, 29 Feb 2000 07:51:46 -0800 (PST) (envelope-from matt@ARPA.MAIL.NET) Received: from epsilon.lucida.qc.ca ([216.95.146.6]) by mail2.uunet.ca with ESMTP id <600153-26033>; Tue, 29 Feb 2000 10:47:38 -0500 Date: Tue, 29 Feb 2000 10:51:23 -0500 From: Matt Heckaman X-Sender: matt@epsilon.lucida.qc.ca To: Brad Knowles Cc: FreeBSD-STABLE Subject: Re: Error: "Maximum file descriptors exceeded"... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Morning, I do not think that MAXUSERS > 128 is a problem at all anymore. I have two very high traffic/load public machines running 3.4-release and 3.4-stable, both have MAXUSERS set at 512 and even NMBCLUSTERS as high as 32,768 - I've never had a drop of trouble out of either of these machines. To be quite honest with you, I'm not very sure where this idea came from that MAXUSERS > 128 is bad, I've been running configs like that for quite a while (I guess ( 3.1+)) and never had a bit of trouble, minus the time I had a hard drive fail, but that doesn't really count =) Hope this helps, Matt -- Matt Heckaman [matt@arpa.mail.net|matt@relic.net] [Please do not send me] !Powered by FreeBSD/x86! [http://www.freebsd.org] [any SPAM (UCE) e-mail] On Tue, 29 Feb 2000, Brad Knowles wrote: : Date: Tue, 29 Feb 2000 10:42:26 -0500 : From: Brad Knowles : To: freebsd-stable@freebsd.org : Subject: Error: "Maximum file descriptors exceeded"... : : Folks, : : I've made some configuration changes on our news peering server : to try to push out more articles to our peers by having more : simultaneous connections open. Unfortunately, I'm now getting this : error quite a lot. : : : I've searched the archives, and although I can find the names of : commands to run to see how many files are currently being used out of : the total (`pstat -T`), and what the current system-wide limits are : (`limit -a`), I've reconfigured the Kernel to artificially raise the : maximum number of open files that are allowed on the system (without : boosting "MAXUSERS" beyond 128, which I understand causes more : problems than it solves), and I've put in a command to set the : per-process limits for the "news" user to be the same as the : system-wide limits, I'm still getting this error. : : Details are below, but I'm at a loss for what more I can do to : make sure that this problem goes away. From what I can tell, there's : nothing more I should need to do in order to make this work : correctly, and yet I still get this error message logged. : : : Any and all help would be appreciated. : : T10e6IA! : : -Brad [.snip.] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message