From owner-freebsd-hackers Wed Jan 27 04:26:14 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA08667 for freebsd-hackers-outgoing; Wed, 27 Jan 1999 04:26:14 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA08662 for ; Wed, 27 Jan 1999 04:26:13 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id VAA12509; Wed, 27 Jan 1999 21:26:03 +0900 (JST) Message-ID: <36AEFF42.16C1ED0D@newsguy.com> Date: Wed, 27 Jan 1999 20:57:54 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Kevin Day , hackers@FreeBSD.ORG Subject: Re: High Load cron patches - comments? References: <199901261853.MAA15095@home.dragondata.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kevin Day wrote: > > > These patches limit the number of jobs cron will start per second, with a > initial burst, a hard limit, as well as a 'burst mode', if the number of > jobs on the 'to do list' is geting excessively high. How do you select which jobs get executed? I fear a DoS attack might be possible unless you somehow prevent a user to always get the same "place" in the execution queue. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com If you sell your soul to the Devil and all you get is an MCSE from it, you haven't gotten market rate. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message