supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Ihor Antonov <>
Subject: Disconnect between s6-svscan and s6-rc
Date: Mon, 24 Oct 2022 16:34:12 -0700	[thread overview]
Message-ID: <20221024233412.4pcy3baje2ly6lsr@localhost> (raw)

Hi Skarnet Supervision Gang :)

I want to run a thing buy you, to udnerstand whether I am not
understanding something or misusing something or is there actually a
problem. Here it goes:

When I do

    s6-rc -u change myservice

the command hangs, waiting for the service to start, keeps the ftfrig
pipe open...

The service does not start, because there is an error in run script.
This can't be caught by compilation phase, in my case there was a
missing env var that prevented a service to start, but I imagine there
can be all sorts of issues with run scripts.

The user of s6-rc gets no error message, and waits forever.
The error message is captured by s6-svscan (or a corresponding logger
for that service) and is either saved into a log file, or printed to a
tty on which svscan is running. 

The user is almost never on the same tty with svscan. The user never
gets an error message from the service, unless they explicitly know
where to look.

It would be nice if a user can get a temporary view into the service's
stdout for the short duration of s6-rc execution? Such that when s6-rc
never exits waiting we can see what the error message that service



             reply	other threads:[~2022-10-24 23:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-24 23:34 Ihor Antonov [this message]
2022-10-25  9:29 ` Laurent Bercot

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20221024233412.4pcy3baje2ly6lsr@localhost \ \ \

* 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).