From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] stop httpd
Date: Thu, 22 Jan 2004 19:55:32 +0000 [thread overview]
Message-ID: <5d31a8e44126e63c2814faf7f2ae8e47@vitanuova.com> (raw)
In-Reply-To: <4d510373a824cbaaa523e2cbd9428825@plan9.bell-labs.com>
> This is stupid. I should merge kill, slay, and Kill.
if you're doing that... it would be quite nice to allow it to accept
process ids as arguments too; trivial but nonetheless useful, i think.
i've sometimes wondered if it might be useful for the output to
contain some sort of annotation to contextualise the process id; e.g.
echo kill>/proc/3090/note # 63628K Rendez emu
useful when one's got several instances of the same (multithreaded)
program running but one only wishes to kill one of them. sometimes
the process id's good enough, but not always.
a quick way to send to notepg too might be useful too.
hmm. 8 lines could quickly become 100!
next prev parent reply other threads:[~2004-01-22 19:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-22 17:08 Matthias Teege
2004-01-22 17:13 ` David Presotto
2004-01-22 18:36 ` Matthias Teege
2004-01-22 19:17 ` Christoph Lohmann
2004-01-22 19:24 ` David Presotto
2004-01-22 19:55 ` rog [this message]
2004-01-23 9:22 ` boyd, rounin
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=5d31a8e44126e63c2814faf7f2ae8e47@vitanuova.com \
--to=rog@vitanuova.com \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).