From: "Ludovic Courtès" <ludo@gnu.org>
To: Oleg Pykhalov <go.wigust@gmail.com>
Cc: "Mathieu Othacehe" <m.othacehe@gmail.com>,
"Clément Lassieur" <clement@lassieur.org>,
26830@debbugs.gnu.org, zimoun <zimon.toutoune@gmail.com>
Subject: [bug#26830] Allow services to implement a 'reload' action
Date: Sat, 26 Mar 2022 21:46:17 +0100 [thread overview]
Message-ID: <87v8w07886.fsf@gnu.org> (raw)
In-Reply-To: <87lewztq2t.fsf@gmail.com> (Oleg Pykhalov's message of "Thu, 24 Mar 2022 16:52:58 +0300")
Hi,
Oleg Pykhalov <go.wigust@gmail.com> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
>
> […]
>
>> I wonder if the patch as-is would achieve that though, because in
>> general those daemons are run with ‘-c /gnu/store/…-config’, so
>> reloading would just reload the same file.
>
> Maybe we could switch to another practice in service definitions:
>
> ‘/gnu/store/...-some-program/bin/some-program -c /etc/some-config’
>
> $ ls -l /etc/static
> /etc/static -> /gnu/store/...-etc/etc
>
> $ ls -l /etc/some-config
> /etc/some-config -> /etc/static/some-config
Hmm yes, we could (I think Maxim did that recently for a service, I
forgot which one.)
I like the clarity of ‘-c /gnu/store/…-config’ better than the ambient
authority and ambiguity of ‘/etc/config’, but I guess we have to made a
tradeoff.
Ludo’.
next prev parent reply other threads:[~2022-03-26 20:47 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-08 15:25 bug#26830: Allow services to implement a 'reload' action Clément Lassieur
2017-05-08 15:28 ` bug#26830: [PATCH 1/4] services: shepherd: " Clément Lassieur
2017-05-08 15:28 ` bug#26830: [PATCH 2/4] gnu: services: nginx: Add " Clément Lassieur
2017-05-08 15:28 ` bug#26830: [PATCH 3/4] gnu: services: prosody: " Clément Lassieur
2017-05-08 15:28 ` bug#26830: [PATCH 4/4] gnu: services: dovecot: " Clément Lassieur
2017-05-09 15:37 ` bug#26830: Allow services to implement " Mathieu Othacehe
2017-05-10 19:31 ` bug#26830: [PATCH] services: shepherd: " Clément Lassieur
2017-05-11 7:13 ` Clément Lassieur
2017-05-11 12:40 ` Clément Lassieur
2017-05-11 12:57 ` Mathieu Othacehe
2017-05-10 19:31 ` bug#26830: " Clément Lassieur
2017-05-11 21:24 ` Ludovic Courtès
2017-05-11 23:08 ` Clément Lassieur
2017-05-12 8:25 ` Ludovic Courtès
2017-05-12 8:57 ` Clément Lassieur
2018-01-28 20:34 ` [bug#26830] " Danny Milosavljevic
2018-01-28 23:23 ` Clément Lassieur
2018-07-11 22:00 ` Ludovic Courtès
2018-07-12 13:06 ` Clément Lassieur
2022-03-23 12:56 ` zimoun
2022-03-24 8:41 ` Ludovic Courtès
2022-03-24 13:52 ` Oleg Pykhalov
2022-03-26 20:46 ` Ludovic Courtès [this message]
2022-03-26 21:14 ` Maxime Devos
2022-03-29 13:36 ` Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v8w07886.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=26830@debbugs.gnu.org \
--cc=clement@lassieur.org \
--cc=go.wigust@gmail.com \
--cc=m.othacehe@gmail.com \
--cc=zimon.toutoune@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).