supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Dewayne Geraghty <dewayne@heuristicsystems.com.au>
To: "supervision@list.skarnet.org" <supervision@list.skarnet.org>
Subject: s6-rc-init verbose equivalent messages?
Date: Thu, 19 Aug 2021 18:45:41 +1000	[thread overview]
Message-ID: <f9063ef4-68a8-7859-47a6-4acedd26536d@heuristicsystems.com.au> (raw)

Is there anyway of tracking down the cause of the following fatal failure?
# /usr/local/bin/s6-rc-init -c /s/comp -l /s/run /s/scan
s6-rc-init: fatal: unable to supervise service directories in
/s/run/servicedirs: No such file or directory

I've completed a disk-disk copy, as I need to integrate s6 into
hardenedbsd.  The compile command works:
# /usr/local/bin/s6-rc-compile -v9 /s/comp /usr/local/etc/s6
...
all good.  But s6-rc-init is stuck, as above.  There are no changes to
the system except IP addresses. I'm baffled!

Regards, Dewayne.

             reply	other threads:[~2021-08-19  8:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-19  8:45 Dewayne Geraghty [this message]
2021-08-19 17:36 ` 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:
  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=f9063ef4-68a8-7859-47a6-4acedd26536d@heuristicsystems.com.au \
    --to=dewayne@heuristicsystems.com.au \
    --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).