supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: "Laurent Bercot" <ska-supervision@skarnet.org>
To: "Xavier Stonestreet" <xstonestreet@gmail.com>,
	supervision@list.skarnet.org
Subject: Re: s6-permafailon not acting as expected
Date: Tue, 17 Nov 2020 21:42:29 +0000	[thread overview]
Message-ID: <em4c63f580-aca9-44d6-9775-885597e12d92@elzian> (raw)
In-Reply-To: <CAK-rGMJGsM2oNgZ0tiS83G8bSZZRdyTk0BLRVPpzn1xrUuE-mA@mail.gmail.com>

>Back to s6-permafailon.c: the sigset_t sigs is not initialized
>either... Looks like it needs a call to sigemptyset().

  Gah! -_- Fixed. Thanks.

--
  Laurent


  parent reply	other threads:[~2020-11-17 21:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-16 18:01 Xavier Stonestreet
2020-11-16 22:05 ` Laurent Bercot
2020-11-17 15:32   ` Xavier Stonestreet
2020-11-17 18:43     ` Xavier Stonestreet
2020-11-17 20:06       ` Xavier Stonestreet
2020-11-17 21:42       ` Laurent Bercot [this message]
2020-11-18 17:22         ` Xavier Stonestreet
2020-11-18 18:35           ` Laurent Bercot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=em4c63f580-aca9-44d6-9775-885597e12d92@elzian \
    --to=ska-supervision@skarnet.org \
    --cc=supervision@list.skarnet.org \
    --cc=xstonestreet@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).