From: Pavel Machek <pavel@suse.cz>
To: "S. Parker" <linux@sparker.net>
Cc: linux-kernel@vger.kernel.org, torvalds@transmeta.com,
marcelo@conectiva.com.br
Subject: Re: Sysrq enhancement: process kill facility
Date: Sat, 9 Feb 2002 21:19:56 +0100 [thread overview]
Message-ID: <20020209201955.GC851@elf.ucw.cz> (raw)
In-Reply-To: <4.2.2.20020208092102.00aa5eb8@10.10.10.29>
In-Reply-To: <4.2.2.20020208092102.00aa5eb8@10.10.10.29>
Hi!
> Here's something that myself and others at Cobalt Networks have found
> useful.
> It extends sysrq to support a way to manually kill a process. In debugging
> situations, we have found times where the system gets wedged, and we'ld like
> to avoid a reboot. Show tasks provides the pid information.
>
> You enter <alt>-<sysrq>-n ("nuke"), and then prompts for the pid. It
> supports
> backspace and control-U. On serial ports, it retains the same semantics:
> a break activates this as a sysrq sequence, but if more than 5-seconds pass
> without any input, it drops out of processing input as a sysrq.
>
> Feedback welcome, please cc: me directly.
Looks good to me; (maybe you could reuse from 'kIll' as killing of all
processes is hardly ever usefull).
Pavel
--
(about SSSCA) "I don't say this lightly. However, I really think that the U.S.
no longer is classifiable as a democracy, but rather as a plutocracy." --hpa
next prev parent reply other threads:[~2002-02-10 21:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-08 17:30 Sysrq enhancement: process kill facility S. Parker
2002-02-08 19:18 ` David Ford
2002-02-09 20:19 ` Pavel Machek [this message]
2002-02-11 19:06 ` S. Parker
[not found] <mailman.1013189761.2392.linux-kernel2news@redhat.com>
2002-02-08 18:19 ` Pete Zaitcev
2002-02-08 21:57 ` Lamont Granquist
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=20020209201955.GC851@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@sparker.net \
--cc=marcelo@conectiva.com.br \
--cc=torvalds@transmeta.com \
/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