On Sat, 12 Jan 2019 11:37:55 +
"Laurent Bercot" wrote:
> >If IBM bails on systemd, is s6/s6-rc ready to take its place? I mean
> >we all know it's ready technically, and is well maintained, but is
> >it ready politically, with help for distro packagers? Perhaps some
> >documentation on best
Hi all,
I think a cool addition to runit program sv and s6's s6-svc would be a
command to send an arbitrary signal to the daemon being supervised.
Let's say a -z was added as an arg to s6-svc or a "genericinterrupt" was
added as an arg to sv. Now you could say:
sv genericinterrupt SIGIO
Laurent Bercot:
The question is, how does systemd decide to proceed with the rest of
the shutdown?
It waits for |s6-svscan| for up to 90s, putting the infamous cylon
warrior and "A stop job is running for s6" message on the console.
After 90s, it starts forcibly killing stuff, not
I _think_ that with my naive current setup, what actually happens is:
- systemd sends a SIGTERM to s6-svscan;
- s6-svscan sends a SIGTERM or SIGHUP to all s6-supervise processes,
depending on what they are supervising, and then runs the finish program;
- the s6-supervise for postgresql sends
I use s6 to supervise userspace services like RabbitMQ and PostgreSQL. The
s6-svscan process is launched and managed by systemd (because it's a CentOS
7 system).
What I would like to do is ensure that PostgreSQL is shut down cleanly when
the system is being powered down or rebooted. Because of the
