From: Ricardo Wurmus <rekado@elephly.net>
To: tomas@tuxteam.de
Cc: "Dr. Arne Babenhauserheide" <arne_bab@web.de>, guile-user@gnu.org
Subject: Re: Fibers web server: use multiple server sockets
Date: Thu, 03 Nov 2022 00:04:47 +0100 [thread overview]
Message-ID: <87pme56jle.fsf@elephly.net> (raw)
In-Reply-To: <Y2LLsi+RTRtUlH+y@tuxteam.de>
tomas@tuxteam.de writes:
> [[PGP Signed Part:Undecided]]
> On Wed, Nov 02, 2022 at 08:35:24PM +0100, Dr. Arne Babenhauserheide wrote:
>>
>> <tomas@tuxteam.de> writes:
>> > As far as I understand Vivien, interfaces come and go during the
>> > server's lifetime. I.e. it's not just a "boot" thing. This seems
>> > like a valid use case.
>> On some servers you might actually pull out an interface during runtime
>> to hotswap a new one — for example because it signaled that it is short
>> of failing.
>
> Yes, but as Vivien explained his case, just the other side of the network
> might go down. Or the dhcp server at the other side takes too long and we
> don't want to block the boot. Or the sysadmin just does "ifdown eth0"
> and somewhat later "ifup...". Or whatever.
Expanding on “whatever”: it may be a virtual network interface. In an
unshared net namespace we can move one end of a veth device into the
container’s net namespace — and we can just as well move it out again or
destroy it by removing its host-side counterpart.
An example of this is shown here:
https://guix.gnu.org/cookbook/en/html_node/Container-Networking.html
--
Ricardo
next prev parent reply other threads:[~2022-11-02 23:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 18:15 Fibers web server: use multiple server sockets dsmich
2022-11-02 18:27 ` Vivien Kraus
2022-11-02 19:19 ` tomas
2022-11-02 19:35 ` Dr. Arne Babenhauserheide
2022-11-02 19:57 ` tomas
2022-11-02 23:04 ` Ricardo Wurmus [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-11-02 16:37 Vivien Kraus
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pme56jle.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=arne_bab@web.de \
--cc=guile-user@gnu.org \
--cc=tomas@tuxteam.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).