From: Alex Efros <powerman@powerman.asdfGroup.com>
Subject: Re: killing an entire process group?
Date: Fri, 9 Jun 2006 12:22:35 +0300 [thread overview]
Message-ID: <20060609092235.GM19319@home.power> (raw)
In-Reply-To: <x3ejxzninq.fsf@nowhere.com>
Hi!
On Thu, Jun 08, 2006 at 07:54:01PM -0700, Adam Megacz wrote:
> Is there any way to tell runit that signals for a supervised service
> must be sent to the entire process group rather than just the
> immediate child of runsv?
>
> I'm specifically trying to get k5start to work. It spawns a
> user-specified process as a child, but periodically reawakens to
> refresh the relevant kerberos/afs credentials. Right now runit sends
> a TERM to k5start, which dies, but then the user process (which was a
> child of k5start) becomes an orphaned process and keeps running
> forever.
Write your own handler of TERM signal.
man runsv (CUSTOMIZE CONTROL section).
--
WBR, Alex.
prev parent reply other threads:[~2006-06-09 9:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-09 2:54 Adam Megacz
2006-06-09 9:22 ` Alex Efros [this message]
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=20060609092235.GM19319@home.power \
--to=powerman@powerman.asdfgroup.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;
as well as URLs for NNTP newsgroup(s).