From owner-freebsd-hackers Sat Feb 2 12:52:41 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 2F4DA37B41A for ; Sat, 2 Feb 2002 12:52:32 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id g12KqOM17214; Sat, 2 Feb 2002 12:52:24 -0800 (PST) (envelope-from dillon) Date: Sat, 2 Feb 2002 12:52:24 -0800 (PST) From: Matthew Dillon Message-Id: <200202022052.g12KqOM17214@apollo.backplane.com> To: Gaspar Chilingarov Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: fork rate limit References: <20020202201551.GA89061@mail.web.am> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :Hi! : :Is it reasonable to administratively limit users' ability to call fork :too other ? Users can take away too much CPU time even if you have :limited them by login.conf 'cputime' limit - just forking lightweight :processes too often. : :If it seems good thing to do, i'll try to code it and submit patches for :-current. : :I think this limit must go to struct uidinfo, am i right ? :Also i need to store per-user counters somewhere, can i place it there? : :-- :Gaspar Chilingarov Well, we did make fork inherit the parent process's current priority, so if a parent process forks() a lot it and its children should get less cpu. Beyond that the system can't really tell whether the cpu use is something the sysad wants (i.e. sa y it's a web server) or something the sysad doesn't want (an abusive user). -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message