Date: Mon, 4 Feb 2002 17:35:51 -0600 From: Dan Nelson <dnelson@allantgroup.com> To: Anthony Schneider <aschneid@mail.slc.edu> Cc: Mike Makonnen <mike_makonnen@yahoo.com>, Gaspar Chilingarov <nm@web.am>, freebsd-hackers@FreeBSD.ORG Subject: Re: fork rate limit Message-ID: <20020204233550.GE88948@dan.emsphone.com> In-Reply-To: <20020204181724.B1633@mail.slc.edu> References: <20020202201551.GA89061@mail.web.am> <200202022052.g12KqOM17214@apollo.backplane.com> <20020202223546.GA430@mail.web.am> <200202030754.g137saC40573@blackbox.pacbell.net> <20020203160433.A10920@mail.slc.edu> <20020203223946.B13336@mail.slc.edu> <20020204175616.A1056@mail.slc.edu> <20020204181724.B1633@mail.slc.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Feb 04), Anthony Schneider said: > I've actually wanted something like this for a while and have considered > coding it myself. Perhaps this could go into a login.conf variable > (which I would have to create myself), but originally my plan was basically > kill off parent processes with the uid of the user who is fork()'ing too > often (200 per 10 seconds sounds good) simply hard-coded. Killing off parent procs could really upset a regular user who is running ./configure, which could easily spawn a couple undred processes in 10 seconds. Maybe simply delay the fork() until the rate drops? -- Dan Nelson dnelson@allantgroup.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020204233550.GE88948>