From: Nathan Dehnel <ncdehnel@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 53225@debbugs.gnu.org
Subject: bug#53225: shepherd freezes if wireguard is started with dns config enabled
Date: Wed, 1 Jun 2022 17:56:04 -0500 [thread overview]
Message-ID: <CAEEhgEvwfB49rpxW-w_hj+xD5MVy-OkT_AmHThNXK1dYW34Fyw@mail.gmail.com> (raw)
In-Reply-To: <87y23eo4lj.fsf@gnu.org>
Just tested and Shepherd 0.9 does not fix this issue.
On Mon, Jan 17, 2022 at 7:48 AM Ludovic Courtès <ludo@gnu.org> wrote:
>
> Hi,
>
> Nathan Dehnel <ncdehnel@gmail.com> skribis:
>
> >>What do you mean by “freezing”? Does ‘herd status’ and similar commands
> > block forever?
> > Yes
> >
> >>Requests in the Shepherd are currently handled sequentially. So if you
> > issue several ‘herd restart’ commands, they’ll be processed one at a
> > time. This is usually okay because ‘start’ commands are expected to be
> > quick (just wait for the daemon to write its PID file or similar).
> > What is the nature of this serialization? Does wireguard need to
> > finish before resolvconf can start? Because that's probably the issue.
>
> One command sent to shepherd by ‘herd …’ must have completed before the
> next one is processed.
>
> You can experience it like this:
>
> sudo herd eval root '(sleep 3)' & echo status && sudo herd status
>
> Here the first ‘herd’ command has shepherd block for 3 seconds, so the
> second ‘herd’ command won’t print anything until 3 seconds have passed.
>
> HTH,
> Ludo’.
next prev parent reply other threads:[~2022-06-01 22:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 0:27 bug#53225: shepherd freezes if wireguard is started with dns config enabled Nathan Dehnel
2022-01-13 15:11 ` Ludovic Courtès
2022-01-13 22:41 ` Nathan Dehnel
2022-01-17 13:48 ` Ludovic Courtès
2022-06-01 22:56 ` Nathan Dehnel [this message]
2022-06-02 13:38 ` Ludovic Courtès
2022-06-08 23:23 ` Nathan Dehnel
2022-06-09 15:05 ` Ludovic Courtès
2022-06-09 15:49 ` Nathan Dehnel
2022-06-09 20:15 ` Ludovic Courtès
[not found] ` <CAEEhgEu2nOL6bEGYxrMdNjU8_Hoex-Xm1DMf4Kxj9M4ZEZ0uRg@mail.gmail.com>
2022-06-13 9:31 ` Ludovic Courtès
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=CAEEhgEvwfB49rpxW-w_hj+xD5MVy-OkT_AmHThNXK1dYW34Fyw@mail.gmail.com \
--to=ncdehnel@gmail.com \
--cc=53225@debbugs.gnu.org \
--cc=ludo@gnu.org \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.