Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 17 Mar 2003 06:47:28 +0200 (EET)
From:      Giorgos Keramidas <keramida@ceid.upatras.gr>
To:        Mike Silbersack <silby@silby.com>
Cc:        src-committers@freebsd.org, cvs-src@freebsd.org, cvs-all@freebsd.org
Subject:   Re: cvs commit: src/sys/vm ... SIGDANGER
Message-ID:  <20030317064452.L38829@gothmog>
In-Reply-To: <20030314160313.O4480@odysseus.silby.com>
References:  <8023.1047662161@critter.freebsd.dk>    <p05200f2bba97e5a92150@[128.113.24.47]> <20030314140414.V4480@odysseus.silby.com>    <p05200f2cba97ef395f0e@[128.113.24.47]> <20030314152510.A4480@odysseus.silby.com> <p05200f2eba97fc3b6b96@[128.113.24.47]> <20030314160313.O4480@odysseus.silby.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 2003-03-14 16:07, Mike Silbersack wrote:
>On Fri, 14 Mar 2003, Garance A Drosihn wrote:
>> Almost all of the suggestions that have come forward are good
>> ideas to do *in addition* to SIGDANGER, but SIGDANGER provides
>> a program with a way to SPECIFICALLY address this very SPECIFIC
>> issue, without having to care what UID it got, or what nice
>
> The problem with SIGDANGER is that only two programs will use it:
>
> 1.  lpd at RPI.
>
> 2.  The forkbomb someone will post to bugtraq the day after we add the
> feature.
>
> I fully agree that there needs to be a way to prioritize processes.
> However, adding an extra signal is just not the way to do it.  If we want
> a manual system like that, let's just add a "don't kill" bit to the proc
> structure which can be set through nice or some other utility by the
> system administrator.

If we do it this way, then we might also make it generic enough and
write pctl(1) as a userland tool that sets 'process properties'.  Then
add to each process a list or bitmap of property bits that would
control the kernel's behavior for that particular process :)

:)


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030317064452.L38829>