From: <tomas@tuxteam.de>
To: guile-user@gnu.org
Subject: Re: Fibers web server: use multiple server sockets
Date: Wed, 2 Nov 2022 20:19:18 +0100 [thread overview]
Message-ID: <Y2LCtjCgZpulob3h@tuxteam.de> (raw)
In-Reply-To: <c3874d5507b67538fffd72884a69ac9d50bdbe15@webmail>
[-- Attachment #1: Type: text/plain, Size: 955 bytes --]
On Wed, Nov 02, 2022 at 06:15:15PM +0000, dsmich@roadrunner.com wrote:
> > From: "Vivien Kraus"
> > To: "guile-user"
> > Sent: Wednesday November 2 2022 12:38:05PM
> > Subject: Fibers web server: use multiple server sockets
>
> > Fibers is a library that I would very much like to use. It provides
> a
> > nice web server. However, as I recently discovered, in a standard
> > GNU/Linux server, not all network interfaces and addresses are up
> when
> > the server is about to start (especially so with dhcp). I have a
> nice
> > solution for that: every now and then, the server calls getaddrinfo.
>
> How about not starting the web server until network interfaces are
> fully up?
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.
You could, of course, restart the server every time an interface
moves...
Cheers
--
t
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2022-11-02 19:19 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 [this message]
2022-11-02 19:35 ` Dr. Arne Babenhauserheide
2022-11-02 19:57 ` tomas
2022-11-02 23:04 ` Ricardo Wurmus
-- 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=Y2LCtjCgZpulob3h@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=guile-user@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.
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).