public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Simon Kirby <sim@netnation.com>
To: "Albert D. Cahalan" <acahalan@cs.uml.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kill(-1,sig)
Date: Sat, 15 Dec 2001 15:09:40 -0800	[thread overview]
Message-ID: <20011215150940.A9612@netnation.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0112141237470.3063-100000@penguin.transmeta.com> <200112151019.fBFAJgS235075@saturn.cs.uml.edu>
In-Reply-To: <200112151019.fBFAJgS235075@saturn.cs.uml.edu>; from acahalan@cs.uml.edu on Sat, Dec 15, 2001 at 05:19:42AM -0500

On Sat, Dec 15, 2001 at 05:19:42AM -0500, Albert D. Cahalan wrote:

> > I do agree, I've used "kill -9 -1" myself.
> 
> This means: EVERYTHING DIE DIE DIE!!!!
> 
> On a Digital UNIX system, I do "/bin/kill -9 -1" often. I expect it to
> kill the shell. This is a nice way to quickly log out and wipe out any
> background processes that might try to save state or continue running.

Exactly.

And then init spawns your getty again, and you log in again, and you
continue doing what you were doing.

Or you could just let it not kill the process doing the killing, and
you'd be more productive.

My point is that I can't see a valid case where we _actually want_ -1 to
send to itself also.  Yes, I know the standards don't mention this.  They
also don't explicity disallow not sending to the originating process, so
I don't see what the big problem is.

Does anybody have a case where including itself is actually useful?

Simon-

[  Stormix Technologies Inc.  ][  NetNation Communications Inc. ]
[       sim@stormix.com       ][       sim@netnation.com        ]
[ Opinions expressed are not necessarily those of my employers. ]

  parent reply	other threads:[~2001-12-15 23:09 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-14 17:34 [PATCH] kill(-1,sig) Andries.Brouwer
2001-12-14 20:25 ` Linus Torvalds
2001-12-17  9:34   ` Chris Wright
2001-12-17 14:41     ` vda
2001-12-17 11:53       ` Sean Hunter
2001-12-17 12:06         ` Matthew Kirkwood
2001-12-17 12:30           ` Sean Hunter
2001-12-17 12:16         ` Miquel van Smoorenburg
2001-12-17 16:06         ` vda
2001-12-14 20:36 ` Simon Kirby
2001-12-14 20:40   ` Linus Torvalds
2001-12-14 20:49     ` Simon Kirby
2001-12-15 10:19     ` Albert D. Cahalan
2001-12-15 14:03       ` Martin Josefsson
2001-12-15 23:09       ` Simon Kirby [this message]
2001-12-16  8:26         ` Albert D. Cahalan
2001-12-17  8:50     ` Helge Hafting
2001-12-17 20:51     ` Udo A. Steinberg
2001-12-17 21:13       ` Linus Torvalds
2001-12-17 22:06         ` Richard B. Johnson
2001-12-18 17:27   ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2001-12-14 21:22 Andries.Brouwer
2001-12-17  7:01 Richard Gooch
2001-12-17 11:41 ` vda
2001-12-17 16:41   ` Richard Gooch
2001-12-17 23:38 Andries.Brouwer

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=20011215150940.A9612@netnation.com \
    --to=sim@netnation.com \
    --cc=acahalan@cs.uml.edu \
    --cc=linux-kernel@vger.kernel.org \
    /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