It seems that s6-svscan and s6-supervise sets SIGPIPE to ignored, which
is fine if that's what they want. But that setting seems to then be
inherited to the entire process tree, which can cause all kinds of weird
problems (very few programs themselves set signal dispositions). Mostly
it's simple sh
s6-dnsip: fatal: unable to resolve fakedomain.org: query still
processing
# echo $?
2
I would expect the tool to return “1” as its exit code, since the
domain exists, but has not A/ record.
You're absolutely right and it was a bug.
Should be fixed in git head; bugfix release coming soon
> It seems that s6-svscan and s6-supervise sets SIGPIPE to ignored
It was a long-time bug indeed, but it has been fixed in 2.10.0.2. :)
If it's still occurring with the latest version of s6, please submit
a strace that illustrates your issue.
--
Laurent
On 17/03/2021 15.03, Laurent Bercot wrote:
>> It seems that s6-svscan and s6-supervise sets SIGPIPE to ignored
>
> It was a long-time bug indeed, but it has been fixed in 2.10.0.2. :)
Thanks, and sorry for the noise. I just grepped the source I happened to
have checked out and found no attempt t
