From: Kyle Meyer <kyle@kyleam.com>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: [PATCH] public-inbox-netd: a multi-protocol superserver
Date: Thu, 05 May 2022 20:18:23 -0400 [thread overview]
Message-ID: <87levfv7hs.fsf@kyleam.com> (raw)
In-Reply-To: <20220505105537.20576-1-e@80x24.org>
Eric Wong writes:
> Since we'll be adding POP3 as our 4th network protocol; asking
> admins to run yet another daemon on top of existing -httpd,
> -nntpd, -imapd is a burden and a waste of system resources
> given the amount of code and file handles shared.
>
> The goal of public-inbox-netd is to be able to replace all
> existing read-only daemons with a single process to save memory
> and reduce administrative overhead; hopefully encouraging more
> users to self-host their own mirrors.
Nice, thanks.
> diff --git a/Documentation/public-inbox-netd.pod b/Documentation/public-inbox-netd.pod
> new file mode 100644
> index 00000000..d6520608
> --- /dev/null
> +++ b/Documentation/public-inbox-netd.pod
[...]
> +=item --key /path/to/key
> +
> +The default private TLS certificate key for optional TLS support
> +if the C<key> option is not given with C<--listen>. The private
> +key may concatenated into the path used by C<--cert>, in which case this
> +option is not needed.
s/may concatenated/may be concatenated/
(It looks like -imapd and -nntpd pods have the same text, and both of
those are also missing this "be".)
next prev parent reply other threads:[~2022-05-06 0:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-05 10:55 [PATCH] public-inbox-netd: a multi-protocol superserver Eric Wong
2022-05-06 0:18 ` Kyle Meyer [this message]
2022-05-07 0:10 ` Eric Wong
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://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87levfv7hs.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=e@80x24.org \
--cc=meta@public-inbox.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).