From: Andreas Schwab <schwab@suse.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Miquel van Smoorenburg <miquels@cistron.nl>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: OLS and console rearchitecture
Date: Tue, 03 Aug 2004 10:44:40 +0200 [thread overview]
Message-ID: <jevfg0fw5j.fsf@sykes.suse.de> (raw)
In-Reply-To: <1091468401.806.0.camel@localhost.localdomain> (Alan Cox's message of "Mon, 02 Aug 2004 18:40:02 +0100")
Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
> On Llu, 2004-08-02 at 17:21, Andreas Schwab wrote:
>> > A configuration file for killall5 in which services/daemons get
>> > defined that should not be signalled ?
>>
>> IMHO a better solution would be some kind of process flag that can be
>> interrogated by killall5.
>
> Policy belongs in user space. This is entirely policy and personal
> preference.
The kernel would only function as a repository and makes sure the flag is
inherited across execve(). Any policy will only be set by user space.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2004-08-03 8:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-02 14:24 OLS and console rearchitecture Jon Smirl
2004-08-02 14:54 ` Alexander E. Patrakov
2004-08-02 16:07 ` Miquel van Smoorenburg
2004-08-02 16:21 ` Andreas Schwab
2004-08-02 17:40 ` Alan Cox
2004-08-03 8:44 ` Andreas Schwab [this message]
2004-08-02 16:16 ` Jon Smirl
2004-08-05 11:08 ` Martin Waitz
2004-08-02 18:33 ` Jesse Barnes
2004-08-03 0:01 ` Benjamin Herrenschmidt
2004-08-05 8:56 ` Helge Hafting
2004-08-05 20:32 ` Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jevfg0fw5j.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=miquels@cistron.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox