supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Steve Litt <slitt@troubleshooters.com>
To: supervision@list.skarnet.org
Subject: Re: s6-ps
Date: Sat, 5 Jan 2019 20:15:03 -0500	[thread overview]
Message-ID: <20190105201503.7f6326f0@mydesk.domain.cxm> (raw)
In-Reply-To: <CADQ2Nw_XqYL9fyaTMSHH3WhuFWt3q=YN2-s2OQ2_XDn5ysG2fg@mail.gmail.com>

On Sat, 5 Jan 2019 18:00:57 -0300
Guillermo <gdiazhartusch@gmail.com> wrote:


> I don't know why execline is a 'recommends' though. It should be a
> 'depends', I believe.

I set up a s6 supervisor using all shellscripts and no execline. You
don't absolutely need execline.

 
SteveT

Steve Litt 
January 2019 featured book: Troubleshooting: Just the Facts
http://www.troubleshooters.com/tjust


  reply	other threads:[~2019-01-06  1:15 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <9f647c4c-2dc3-b977-928c-ee164ba88afe@ntlworld.com>
2019-01-05  0:20 ` s6-ps Laurent Bercot
2019-01-05  4:04   ` s6-ps Jonathan de Boyne Pollard
2019-01-05 10:46   ` s6-ps Jonathan de Boyne Pollard
2019-01-05 14:41     ` s6-ps Jonathan de Boyne Pollard
2019-01-05 15:29     ` s6-ps multiplexd
2019-01-05 20:30     ` Can s6 be enough?: was s6-ps Steve Litt
2019-01-05 21:22       ` Laurent Bercot
     [not found]         ` <20190106053901.GA16647@latitude.localdomain>
2019-01-06  7:40           ` Laurent Bercot
2019-01-06 15:03       ` Brett Neumeier
2019-01-07 21:45         ` Steve Litt
2019-01-08  9:19           ` Laurent Bercot
2019-01-05 21:00     ` s6-ps Guillermo
2019-01-06  1:15       ` Steve Litt [this message]
2019-01-06  7:06       ` s6-ps Colin Booth
2019-01-06  7:30         ` s6-ps Laurent Bercot
2019-01-06 18:07           ` s6-ps Colin Booth
2019-01-04  9:18 s6-ps 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=20190105201503.7f6326f0@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).