From: Pete Zaitcev <zaitcev@redhat.com>
To: linux@sparker.net, linux-kernel@vger.kernel.org
Subject: Re: Sysrq enhancement: process kill facility
Date: Fri, 8 Feb 2002 13:19:25 -0500 [thread overview]
Message-ID: <200202081819.g18IJPa22033@devserv.devel.redhat.com> (raw)
In-Reply-To: <mailman.1013189761.2392.linux-kernel2news@redhat.com>
In-Reply-To: <mailman.1013189761.2392.linux-kernel2news@redhat.com>
> 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.
I am afraid we'll have bash and perl in kernel before too long,
if this avenue is to be pursued.
Why don't you use something like SGI kdb for debugging kernels?
-- Pete
next parent reply other threads:[~2002-02-08 18:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1013189761.2392.linux-kernel2news@redhat.com>
2002-02-08 18:19 ` Pete Zaitcev [this message]
2002-02-08 21:57 ` Sysrq enhancement: process kill facility Lamont Granquist
2002-02-08 17:30 S. Parker
2002-02-08 19:18 ` David Ford
2002-02-09 20:19 ` Pavel Machek
2002-02-11 19:06 ` S. Parker
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=200202081819.g18IJPa22033@devserv.devel.redhat.com \
--to=zaitcev@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@sparker.net \
/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