[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug#62802] [PATCH 0/4] Add reload action to syslog service.
From: |
Ludovic Courtès |
Subject: |
[bug#62802] [PATCH 0/4] Add reload action to syslog service. |
Date: |
Fri, 21 Apr 2023 16:03:37 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux) |
Hi!
Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
[...]
>> I’m really not a fan of static configuration file names: you can never
>> be sure what config the service is using—compare this with the
>> unambiguous ‘--config=/gnu/store/…example.conf’.
>
> Right; although now if you aren't sure what is used you can 'reload' it,
> eh :-).
True. :-) The other issue is that that makes it impossible to run
several instances of the service (not a problem for syslogd of course,
but could be an issue elsewhere).
>> With the Shepherd in ‘master’, there’s a hook to change a service’s
>> “running value” so it should be possible to stop the previous process,
>> start a new one, and update the service’s running value (which is not
>> equivalent to SIGHUP, but maybe good enough for some cases).
>
> Wouldn't that be equivalent to restarting the service? I wasn't aware
> of the new hook facility, I'll have to read on it, thanks!
There’s nothing to read :-) and it wasn’t designed with that use case in
mind, but we’ll see.
>> A simpler approach might be run the service in a container with
>> /gnu/store/…conf mapped to a fixed location, and somehow update that
>> mapping as we go. Food for thought!
>
> Interesting idea... although it'd only be compatible with Linux and I
> dislike writing special cases in services (or anywhere if I can help
> it).
Yeah.
Ludo’.