public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <willy@w.ods.org>
To: unlisted-recipients:; (no To-header on input)
Cc: Alexey Dobriyan <adobriyan@gmail.com>,
	Chris Boot <bootc@bootc.net>,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC] un petite hack: /proc/*/ctl
Date: Tue, 29 Nov 2005 06:53:10 +0100	[thread overview]
Message-ID: <20051129055310.GS11266@alpha.home.local> (raw)
In-Reply-To: <20051129054819.GR11266@alpha.home.local>

On Tue, Nov 29, 2005 at 06:48:19AM +0100, Willy Tarreau wrote:
> On Tue, Nov 29, 2005 at 04:33:54AM +0300, Alexey Dobriyan wrote:
> > On Tue, Nov 29, 2005 at 12:23:19AM +0000, Chris Boot wrote:
> > > On 29 Nov 2005, at 0:28, Alexey Dobriyan wrote:
> > > >echo kill >/proc/$PID/ctl
> > > >	send SIGKILL to process
> > > >
> > > >echo term >/proc/$PID/ctl
> > > >	send SIGTERM to process
> > >
> > > Pardon me for my ignorance, but what's wrong with the following?
> > >
> > > kill -KILL $PID
> > >     and
> > > kill -TERM $PID
> > 
> > kill(1) existence.
> 
> This is non sense, kill is included in the shell ! And if you need to
> agressively reduce a binary size, a simple call to kill() will be
> shorter than sprintf(), open(), write(), close().
> 
> > Not that I'm seriously proposing patch for inclusion.
> 
> so please don't pollute the list with useless patches that take time
> to review.

Sorry, I've just noticed that you marked the subject "[RFC]" and not
"[PATCH]". Anyway I still find it useless :-)

Regards,
Willy


  reply	other threads:[~2005-11-29  5:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-29  0:28 [RFC] un petite hack: /proc/*/ctl Alexey Dobriyan
2005-11-29  0:23 ` Chris Boot
2005-11-29  1:33   ` Alexey Dobriyan
2005-11-29  5:48     ` Willy Tarreau
2005-11-29  5:53       ` Willy Tarreau [this message]
2005-11-29  7:26         ` Denis Vlasenko
2005-11-30 10:21       ` Folkert van Heusden
2005-11-30 21:23         ` Willy Tarreau
2005-12-09 14:24           ` Jan Engelhardt
2005-12-15  3:58             ` Kyle Moffett

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=20051129055310.GS11266@alpha.home.local \
    --to=willy@w.ods.org \
    --cc=adobriyan@gmail.com \
    --cc=bootc@bootc.net \
    --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