supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Oliver Schad <oliver.schad@automatic-server.com>
To: supervision@list.skarnet.org
Subject: Systemd unit parser and s6 generator
Date: Mon, 27 Feb 2023 17:25:16 +0100	[thread overview]
Message-ID: <20230227172516.0d4bb760@flunder.oschad.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 961 bytes --]

Hi everybody

I don't know, if somebody has tried that ever. However we want to
continue to use Ubuntu on s6 and packages today our s6 "units" manually.

We've build a generator for that, that creates a base of service. But
the call of this generator is once by a human being which manually
decides which options make sense. Later he/she modifies maybe the
generated result.

We've discussed internally if we change that process and try to write a
systemd unit parser, because all units are there in Ubuntu.

If we could catch 90% of all cases, we need, we would be happy.
If it would take 2 weeks of work, that would be fine.

Did somebody of you try to implement something? What are your thoughts?

Best Regards
Oli

-- 
Automatic-Server AG •••••
Oliver Schad
Geschäftsführer
Hardstr. 46
9434 Au | Schweiz

www.automatic-server.com | oliver.schad@automatic-server.com
Tel: +41 71 511 31 11 | Mobile: +41 76 330 03 47

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

             reply	other threads:[~2023-02-27 16:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-27 16:25 Oliver Schad [this message]
2023-02-28  2:02 ` Laurent Bercot
2023-04-24  8:06   ` Laurent Bercot
2023-04-09  7:43 ` Jonathan de Boyne Pollard

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=20230227172516.0d4bb760@flunder.oschad.de \
    --to=oliver.schad@automatic-server.com \
    --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).