From: Steve Litt <slitt@troubleshooters.com>
To: supervision@list.skarnet.org
Subject: Re: Generic interrupt command?
Date: Sat, 2 Feb 2019 16:40:42 -0500 [thread overview]
Message-ID: <20190202164042.20551e42@mydesk.domain.cxm> (raw)
In-Reply-To: <20190202210810.qckhzw4zgfxui6u3@cathexis.xen.prgmr.com>
On Sat, 2 Feb 2019 21:08:10 +0000
Colin Booth <colin@heliocat.net> wrote:
> On Sat, Feb 02, 2019 at 02:30:14PM -0500, Steve Litt wrote:
> > On Sat, 02 Feb 2019 09:07:31 +0000
> > "Laurent Bercot" <ska-supervision@skarnet.org> wrote:
> >
> > ====================================================
> > kill -s SIGKILL `sv pid agetty-tty6`
> > ====================================================
> >
> > I don't know if the s6-svc command already has the equivalent of a
> > hypothetical sv "pid" command, but if it doesn't, I imagine it
> > would be easy to put in and very helpful to those forging
> > shellscripts.
> >
> > By adding this little addition to s6-svc (and hopefully sv if Gerrit
> > can scrape together the time), no hackiness would be added to s6 or
> > runit: Any hackiness would be in the shellscript created by the
> > programmer using s6 or runit.
> >
> As documented here: https://www.skarnet.org/software/s6/s6-svstat.html
>
> s6-svstat -p /path/to/service | xargs kill SIGNAL
>
Cool. That's all that's needed.
SteveT
--
Steve Litt
January 2019 featured book: Troubleshooting: Just the Facts
http://www.troubleshooters.com/tjust
next prev parent reply other threads:[~2019-02-02 21:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-02 2:36 Steve Litt
2019-02-02 9:07 ` Laurent Bercot
2019-02-02 19:30 ` Steve Litt
2019-02-02 21:08 ` Colin Booth
2019-02-02 21:40 ` Steve Litt [this message]
2019-02-05 3:09 ` John O'Meara
2019-02-05 4:15 ` Roger Pate
2019-02-05 7:20 ` Laurent Bercot
2019-02-05 14:16 ` John O'Meara
2019-02-05 19:30 ` Laurent Bercot
2019-02-10 4:14 ` John O'Meara
2019-02-10 11:41 ` Laurent Bercot
2019-02-02 22:31 ` Jonathan de Boyne Pollard
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=20190202164042.20551e42@mydesk.domain.cxm \
--to=slitt@troubleshooters.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).