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 <ihor@antonovs.family>
To: supervision@list.skarnet.org
Subject: s6-rc user experience question
Date: Sat, 15 Oct 2022 23:28:22 -0700	[thread overview]
Message-ID: <20221016062822.ohngiq54sr2qhti3@localhost> (raw)

Hi Laurent, hi list.

I've been trying to get s6-rc set up and after some time I think I
managed it. I want to describe my process as a list of steps and then
ask you for comments. So here it goes:

1. First we create 'scandir1', and put services there. Each service is a
   svcdir. We put dependencies file and type file in each svcdir.
   (We do not run svcscn on it, because it doesn't really manage
   dependencies)

2. We run s6-rc-compile pointing at scandir and get 'compiled' dir as
   output.

3. We run svcscan process on an emtpy dir - 'scandir2'

4. We run s6-rc-init , feeding 'compiled' and 'scandir2' dirs  we
   get 'live' dir.

At this point things seem to be working and I can use s6-rc to bring up
and down services with dependencies. But this gets very confusing and
does not look like a good user experience:

- The contents of scandir1 and scandir2 look very
similar (scandir2 differs only by the fact that it has symlinks instead
of regular svcdirs).

- Complied dir contains copies of scandir1 services plus some files

- Live dir is the most wired one. It has symlinks to compiled and
  scandir2 and it also has copies of services under servicedirs/
  directory

So same information is duplicated 3 times and symlinked 3 times.
Is this the intended flow? Or have I messed something up really badly?


Thanks

Ihor

             reply	other threads:[~2022-10-16  6:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-16  6:28 Ihor Antonov [this message]
2022-10-16 10:39 ` Laurent Bercot
2022-10-16 16:02   ` Ihor Antonov
2022-10-17 13:11     ` Laurent Bercot
2022-10-17 15:43       ` Ihor Antonov
2022-10-17 21:32         ` Laurent Bercot
2022-10-18  1:13         ` Alexis
2022-10-18  3:14           ` Ihor Antonov

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=20221016062822.ohngiq54sr2qhti3@localhost \
    --to=ihor@antonovs.family \
    --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).