From: steinex <steinex@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] tor: fix Failing because we run out of file handles
Date: Wed, 05 May 2021 02:44:32 +0200 [thread overview]
Message-ID: <20210505004432.PJeev7xMcOvxZbv3Wcgmjs-SVtTUohDC-_esVWqkLZI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30687@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 410 bytes --]
New review comment by steinex on void-packages repository
https://github.com/void-linux/void-packages/pull/30687#discussion_r626195426
Comment:
I'd prefer to not push this too far far for now, I will see how it holds up in production. This is not HAProxy and is pretty intensive on CPU resources. I'm open to up this again if this problem will pop up again, but you need some really beefy hardware for that.
next prev parent reply other threads:[~2021-05-05 0:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-05 0:35 [PR PATCH] " steinex
2021-05-05 0:38 ` [PR REVIEW] " ericonr
2021-05-05 0:44 ` steinex [this message]
2021-05-05 0:52 ` steinex
2021-05-05 2:12 ` [PR PATCH] [Merged]: " ericonr
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=20210505004432.PJeev7xMcOvxZbv3Wcgmjs-SVtTUohDC-_esVWqkLZI@z \
--to=steinex@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 NNTP newsgroup(s).