While it is unwise to transform shutdown signals in s6-supervise [1], I
think the customisation is achievable in s6-rc by adding a file in the
service definition directory which specifies the signal (defaults to
SIGTERM) to send to the daemon process. Any comments on this?
[1]
I just realised that we can set up a oneshot for the disjunction with
its dependencies being the intersection of the dependencies of all
services in the disjunction, with the `up' and `down' being something
like `s6-svwait -o -[ud] srv1 srv2 ...' ([ud]: `u' for `up', `d' for
`down'), so perhaps no
Hi!
On Mon, May 01, 2017 at 11:11:25PM +0200, Francisco Gómez wrote:
> "It's old software. Its last version is from 2014. If I have to
> choose between a dynamic, bug-filled init like Systemd and a barely
> maintained init like Runit, I'd rather use Systemd."
>
> That sounds bad,
Hello there, nice to meet you! If you don't mind, I'll be quite too
straight and tell you what I'm coming for.
So, a few days ago, I switched to Void Linux. This not only meant that
my hipster non-mainstream levels had increased over 9000, but that I
had switched from Systemd to Runit as well. At
