From: "Daniel Clark" <dclark@pobox.com>
To: supervision@list.skarnet.org
Subject: Re: How to kill runsv, no matter what?
Date: Wed, 28 Feb 2007 18:24:49 -0500 [thread overview]
Message-ID: <5422d5e60702281524i5181f88dmdbcc77039ae98031@mail.gmail.com> (raw)
In-Reply-To: <m3vehsbu77.fsf@multivac.cwru.edu>
On 2/23/07, Paul Jarc <prj@po.cwru.edu> wrote:
> "Daniel Clark" <dclark@pobox.com> wrote:
> > Okay, so let's assume we have a service that does not have this "bug",
> > but that is running and shouldn't be force killed (e.g. we want to
> > wait until sleep times out, or until some non-atomic process is
> > complete). Is there any way to block until that happens?
>
> sv -v
> http://smarden.org/runit/sv.8.html
Thanks; I now have a package of runit that I can
install/uninstall/reinstall consistently without leaving anything
behind. It uses a combination of sv -v (to avoid the problem) on
package remove, and a kill pipeline (not yet tested on *nix other than
GNU/Linux) on install. Sort of ugly, but it works.
If anyone else uses encap, the package is up at:
http://tinyurl.com/2nrdx7
It works for running runit's runsvdir under inittab or upstart control.
--
Daniel Clark # http://dclark.us # http://opensysadmin.com
prev parent reply other threads:[~2007-02-28 23:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-21 20:14 Daniel Clark
2007-02-21 21:04 ` Daniel Clark
2007-02-23 3:51 ` Daniel Clark
2007-02-23 12:02 ` Laurent Bercot
2007-02-23 14:05 ` Gerrit Pape
2007-02-23 14:24 ` Alex Efros
2007-02-23 17:40 ` Daniel Clark
2007-02-23 17:32 ` Daniel Clark
2007-02-23 17:39 ` Paul Jarc
2007-02-23 17:46 ` Daniel Clark
2007-02-23 17:59 ` Paul Jarc
2007-02-23 18:25 ` Daniel Clark
2007-02-23 18:32 ` Paul Jarc
2007-02-28 23:24 ` Daniel Clark [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=5422d5e60702281524i5181f88dmdbcc77039ae98031@mail.gmail.com \
--to=dclark@pobox.com \
--cc=supervision@list.skarnet.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;
as well as URLs for NNTP newsgroup(s).