From owner-freebsd-hardware Sun Sep 27 23:57:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA13094 for freebsd-hardware-outgoing; Sun, 27 Sep 1998 23:57:32 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from home.dragondata.com (home.dragondata.com [204.137.237.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA13089 for ; Sun, 27 Sep 1998 23:57:29 -0700 (PDT) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.8/8.8.5) id BAA01249; Mon, 28 Sep 1998 01:57:17 -0500 (CDT) From: Kevin Day Message-Id: <199809280657.BAA01249@home.dragondata.com> Subject: Re: Server Stability not good anymore In-Reply-To: from "Jan B. Koum" at "Sep 27, 98 11:53:51 pm" To: jkb@best.com (Jan B. Koum) Date: Mon, 28 Sep 1998 01:57:17 -0500 (CDT) Cc: clash@tasam.com, freebsd-hardware@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Uhm.. it is somewhat your fault if you let your users to use as > much memory as they want. :) They are users and don't know any better > (nice? what nice?). > > I'd suggest limiting memory and cpu to your users via login class > features (look at /etc/login.conf). Thanks, > This should probably be moved to freebsd-isp if we go any further here... :) No, we don't let them run free.... Most users are limited to one background process (must stay under 2MB) or some software we have goes through and kills it. I don't mind them (temporarily) eating up ram, but nothing for more than 10-15 mins. We're using login.conf to limit CPU usage already. (eggdrop seems to have a bug where it'll go nuts and sit in a loop.... the cpu limit kills them rather easily). Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message