From owner-freebsd-questions Mon Nov 27 21:31:28 2000 Delivered-To: freebsd-questions@freebsd.org Received: from keep.scn.ru (SCN-SibInet.sibinet.ru [213.24.217.138]) by hub.freebsd.org (Postfix) with ESMTP id A52CD37B4F9; Mon, 27 Nov 2000 21:31:22 -0800 (PST) Received: from scn.ru (alx.sc.ten [10.0.0.13]) by keep.scn.ru (8.9.3/8.9.3) with ESMTP id MAA14143; Tue, 28 Nov 2000 12:31:55 +0700 (KRAT) (envelope-from alx@scn.ru) Message-ID: <3A23437E.189E8C7B@scn.ru> Date: Tue, 28 Nov 2000 12:32:46 +0700 From: "Alex N. Zhuravlev" Organization: SCT X-Mailer: Mozilla 4.76 [en] (Win98; U) X-Accept-Language: ru,en MIME-Version: 1.0 To: freebsd-questions@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG Subject: Limiting script memory usage Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi ! I've recently got a proplem. I am running Apache on FreeBSD and maintaining virtual web-servers. For each server there is a specific user, and using apache suexec, cgi cripts are running from those specific users. One of them got a perl script with memory leak - so script gets all the memory, than swap and hangs all the host at final. Here is the question: is there any way to limit resourses via OS (memory, cpu) for that specific user or group/class of users ? I've tried to make a group in login.conf: ------------------------------------------------------------------------- webcl|Web clients:\ :cputime=30m:\ :datasize=8M:\ :stacksize=2M:\ :memorylocked=4M:\ :memoryuse=8M:\ ------------------------------------------------------------------------- and assigning those users to login class webcl. This doesn't help - again script tooks all the memory. Scripts are running from Apache, so using nice and limit, I guess, is unappliable. Maybe somebody has got a solution ??? Answer please direct, cause I am out of freebsd-questions now. Thanks for any help. Alex N. Zhuravlev. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message