From: "Ludovic Courtès" <ludo@gnu.org>
To: Nathan Dehnel <ncdehnel@gmail.com>
Cc: 53225@debbugs.gnu.org
Subject: bug#53225: shepherd freezes if wireguard is started with dns config enabled
Date: Thu, 02 Jun 2022 15:38:56 +0200 [thread overview]
Message-ID: <87o7zbp4lr.fsf@gnu.org> (raw)
In-Reply-To: <CAEEhgEvwfB49rpxW-w_hj+xD5MVy-OkT_AmHThNXK1dYW34Fyw@mail.gmail.com> (Nathan Dehnel's message of "Wed, 1 Jun 2022 17:56:04 -0500")
Hi Nathan,
Nathan Dehnel <ncdehnel@gmail.com> skribis:
> Just tested and Shepherd 0.9 does not fix this issue.
Could you be more specific? Specifically, could you share
/var/log/messages for the parts related to Wireguard?
> On Mon, Jan 17, 2022 at 7:48 AM Ludovic Courtès <ludo@gnu.org> wrote:
[...]
>> 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.
This is actually still the case with 0.9, because here we’re calling
(@ (guile) sleep), which blocks. So… not a good example.
The short story is: it is still possible to write code that blocks
shepherd, as with the ‘sleep’ example above. However, the standard
service constructors/destructors no longer block, and shepherd can serve
multiple clients concurrently.
Ludo’.
next prev parent reply other threads:[~2022-06-02 13:40 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
2022-06-02 13:38 ` Ludovic Courtès [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o7zbp4lr.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=53225@debbugs.gnu.org \
--cc=ncdehnel@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).