From: Ihor Antonov <ihor@antonovs.family>
To: Peter Shkenev <petershh@disroot.org>
Cc: supervision@list.skarnet.org
Subject: Re: s6-rc as user service manager
Date: Mon, 17 Oct 2022 16:49:05 -0700 [thread overview]
Message-ID: <20221017234905.4rrdwvrxs6pchfdx@localhost> (raw)
In-Reply-To: <8F72C59D-7F58-4084-94B4-CBEF75421327@disroot.org>
On 2022-10-17 23:42, Peter Shkenev wrote:
> ...
> 1) User services are services running as a given user and started at a
> boot time
> This option is a trivial one with s6.
>
> 2) User services are services defined by users and running supervised
> when the user wants it.
> You can implement this with s6-usertree-maker [1], which would provide
> you with a supervision tree rooted in a system one which can be managed
> by user. User will have its own scandir and they can use all commands
> provided by s6/s6-rc on their scandir.
Thanks Peter, this was actually helpful and enchanced my mental model.
I think I get get away for now with a user's tree rooted in the system
tree. My graphics environment (sway) can start necessary services
when it is started.
> > - Minor: a test utility for svscan dir would be nice
> > - Minor: a test utility for live dir would be nice
>
> If you use s6-rc, those are the same directories, filled by s6-rc-init
> and changed by s6-rc-update. So the test would actually test those
> utilities, I guess.
By testing I meant checking if the directory has an active process
watching it. I believe there is a function in skalibs fd_lock [1]
that svscan uses to check if another svscan runs there. I think it is
just a matter of exposing that function as standalone executable.
[1] https://github.com/skarnet/skalibs/blob/master/src/libstddjb/fd_lock.c
Ihor
next prev parent reply other threads:[~2022-10-17 23:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 17:50 Ihor Antonov
2022-10-17 20:42 ` Peter Shkenev
2022-10-17 23:49 ` Ihor Antonov [this message]
2022-10-18 0:58 ` Laurent Bercot
2022-10-18 3:12 ` 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=20221017234905.4rrdwvrxs6pchfdx@localhost \
--to=ihor@antonovs.family \
--cc=petershh@disroot.org \
--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).