From owner-freebsd-isp Mon Aug 20 13:47:34 2001 Delivered-To: freebsd-isp@freebsd.org Received: from vcnet.com (mail.vcnet.com [209.239.239.15]) by hub.freebsd.org (Postfix) with SMTP id 08BD537B41E for ; Mon, 20 Aug 2001 13:47:25 -0700 (PDT) (envelope-from jpr@vcnet.com) Received: (qmail 54937 invoked by uid 1001); 20 Aug 2001 20:47:07 -0000 Date: Mon, 20 Aug 2001 13:47:07 -0700 From: Jon Rust To: freebsd-isp@FreeBSD.ORG Subject: login class defs for web users Message-ID: <20010820134707.B42652@mail.vcnet.com> Mail-Followup-To: freebsd-isp@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: http://www.freebsd.org/ Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I hadn't really paid much attention to login classes before. Recently however, I see the need for it cuz I've had a few runaway customer CGIs. So I'm looking at implementing some limits and was wondering what other hosting folks are using for their web users. I don't want to start throwing limits in there and adversely effect current users. Basically i want limits that prevent things like the runaway perl CGI process the other day that had my workload pegged at 8, and memory usage at 99%. Tips and 'gotchas' appreciated. Thanks, jon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message