public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Henrik Brix Andersen <brix@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] init scripts and custom signals
Date: Mon, 9 Jan 2006 13:40:33 +0100	[thread overview]
Message-ID: <20060109124032.GA30466@osgiliath.brixandersen.dk> (raw)
In-Reply-To: <200601091232.32522.uberlord@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 707 bytes --]

On Mon, Jan 09, 2006 at 12:32:32PM +0000, Roy Marples wrote:
> So, the question now must be, do we allow start-stop-daemon to defy calling 
> logic and NOT stop a daemon? How do we know we're not supposed to stop the 
> daemon based on a custom signal? The answer is we can't. So instead of
> 
> start-stop-daemon --stop -s HUP -p /var/run/dnsmasq.pid
> 
> we need to write
> 
> kill -s HUP $(< /var/run/dnsmasq.pid)

... or implement a stand-alone --signal (or -s) in start-stop-daemon,
allowing it to be called like this:

start-stop-daemon --signal HUP -p /var/run/dnsmasq.pid

Regards,
Brix
-- 
Henrik Brix Andersen <brix@gentoo.org>
Gentoo Metadistribution | Mobile computing herd

[-- Attachment #2: Type: application/pgp-signature, Size: 211 bytes --]

  reply	other threads:[~2006-01-09 12:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-09 12:32 [gentoo-dev] init scripts and custom signals Roy Marples
2006-01-09 12:40 ` Henrik Brix Andersen [this message]
2006-01-09 12:49   ` Roy Marples
2006-01-09 14:22 ` Mike Frysinger
2006-01-09 16:05   ` Henrik Brix Andersen
2006-01-09 16:32   ` Roy Marples
2006-01-09 16:59     ` Henrik Brix Andersen
2006-01-10 17:33   ` Roy Marples
2006-01-10  8:19 ` [gentoo-dev] baselayout 1.12 and runlevel changes Was: " Duncan
2006-01-10 11:31   ` Roy Marples
2006-01-10 17:11     ` [gentoo-dev] " Duncan
2006-01-10 17:22       ` Roy Marples

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=20060109124032.GA30466@osgiliath.brixandersen.dk \
    --to=brix@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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