2017-10-29 22:24 GMT-03:00 Guillermo:
>
> [...] or to call a program that does this reboot(RB_POWERCYCLE) thing
> on FreeBSD, if it's implemented.
Scratch this part; it would have to be called by the stage3 init, not
the SIGWINCH handler. But it was an example, the rest of the message
still stands
2017-10-29 18:01 GMT-03:00 Laurent Bercot:
>
> Maybe, if it's needed. SIGWINCH is not POSIX, and I'd rather not have
> s6 exhibit different behaviours on systems where it's not supported
> (same reason why I'm reluctant to add pid namespace support to
> s6-supervise). If there's a way to make it e
I'm curious, could you elaborate on the part about package updates and
race conditions?
Updating a live service directory is difficult.
- You want updates to be atomic. If they're not, and for some
reason there's a failure mid-update, recovering may be very painful.
- Service directories ar
Which reminds me, are there any plans to add SIGWINCH to the set of
signals that 's6-svscan -s' can divert?
Maybe, if it's needed. SIGWINCH is not POSIX, and I'd rather not have
s6 exhibit different behaviours on systems where it's not supported
(same reason why I'm reluctant to add pid namespa
(Quoting this e-mail for context)
2017-10-29 5:37 GMT-03:00 Jonathan de Boyne Pollard:
>
> Since SIGWINCH to process #1 is already taken by Linux, I have adjusted my
> softwares to use SIGRTMIN+7 and SIGRTMIN+17 for the signals to process #1
> for this, ready for when Linux eventually catches up w
Hello,
2017-10-29 6:58 GMT-03:00 Laurent Bercot:
>
> - Void does not use a copy of the service directories in a tmpfs.
> It only has one instance of the service directories, in /etc/sv.
> (I don't recommend that setup, in particular because it makes it
> difficult to implement a package update wi
In runit on Void Linux, what is the purpose of these supervise dir
symlinks?
I don't know Void so I can't tell for sure, but the logical
explanation that comes to mind is the following:
- Void does not use a copy of the service directories in a tmpfs.
It only has one instance of the service d
Perhaps runit just does not care, just like what s6 seems to do?
On Sun, Oct 29, 2017 at 05:35:22AM -0400, Steve Litt wrote:
> Are these symlinks a Void Linux implementation thing, or are they
> specified in runit itself?
--
My current OpenPGP key:
RSA4096/0x227E8CAAB7AA186C (expires: 2020.10.19
Hi all,
On my Void Linux machine, whose runit system was installed by the
void-installer program on OS installation, each daemon's supervise
directory is really just a symlink to a supervise directory
in /run/runit. In other words:
[root@mydesk /]# ls -ldF /etc/sv/alsa/supervise
lrwxrwxrwx 1 root
Warner Losh, FreeBSD and embedded systems developer, has just invented a
new shutdowngoal, in addition to the ones that we already know. In
addition to the conventional reset, power off, halt, and kexec goals; xe
has added a power-off-and-then-on-again goal. Xe has named it power
cycle, and i
10 matches
Mail list logo
