From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=-1.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID,
	DKIM_VALID_AU,MAILING_LIST_MULTI autolearn=ham autolearn_force=no
	version=3.4.4
Received: (qmail 12696 invoked from network); 16 Oct 2022 06:28:03 -0000
Received: from alyss.skarnet.org (95.142.172.232)
  by inbox.vuxu.org with ESMTPUTF8; 16 Oct 2022 06:28:03 -0000
Received: (qmail 26302 invoked by uid 89); 16 Oct 2022 06:28:26 -0000
Mailing-List: contact supervision-help@list.skarnet.org; run by ezmlm
Sender: <supervision@list.skarnet.org>
Precedence: bulk
List-Post: <mailto:supervision@list.skarnet.org>
List-Help: <mailto:supervision-help@list.skarnet.org>
List-Unsubscribe: <mailto:supervision-unsubscribe@list.skarnet.org>
List-Subscribe: <mailto:supervision-subscribe@list.skarnet.org>
List-Id: <supervision.list.skarnet.org>
Received: (qmail 26295 invoked from network); 16 Oct 2022 06:28:25 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=antonovs.family;
	s=20200215; t=1665901673;
	h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
	 to:to:cc:mime-version:mime-version:content-type:content-type;
	bh=ySi4JvbN5iZxm584cAmEaciUzsTwBdwqStefcEhdVYo=;
	b=KNCHA6AEI9zvKOMq5m+nnY+3dfisP0/AoWunU+ba3K5aIyciYh6vAK1+fcsrY0KYeZwBSV
	1/0Q9eUe4sHyW4mhp4s/laCIv95+2zfTFSdu3/+Uphsb7cLjZTvOurCPDkPBJELloaK3IR
	ThLKNakRVY8tVuKG16nGVbaEXYZD/vY=
Date: Sat, 15 Oct 2022 23:28:22 -0700
From: Ihor Antonov <ihor@antonovs.family>
To: supervision@list.skarnet.org
Subject: s6-rc user experience question
Message-ID: <20221016062822.ohngiq54sr2qhti3@localhost>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline

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