From: steinex <steinex@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] tor: raise max open files again
Date: Fri, 22 Jul 2022 11:18:41 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38188@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1434 bytes --]
There is a new pull request by steinex against master on the void-packages repository
https://github.com/steinex/void-packages tor
https://github.com/void-linux/void-packages/pull/38188
tor: raise max open files again
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
The current max open files is still not quite enough when running a high speed relay. Raise to 65536 which is also the default in Debian.
Failing test on x86_64-musl is known.
cc @daniel-eys
<!--
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
A patch file from https://github.com/void-linux/void-packages/pull/38188.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-tor-38188.patch --]
[-- Type: text/x-diff, Size: 1003 bytes --]
From a5765b909a5eff0f8dccca24f745a493acae8753 Mon Sep 17 00:00:00 2001
From: Frank Steinborn <steinex@nognu.de>
Date: Fri, 22 Jul 2022 11:08:52 +0200
Subject: [PATCH] tor: raise max open files again
---
srcpkgs/tor/files/tor/run | 2 +-
srcpkgs/tor/template | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/tor/files/tor/run b/srcpkgs/tor/files/tor/run
index 389850ff0342..3b6f9953376d 100755
--- a/srcpkgs/tor/files/tor/run
+++ b/srcpkgs/tor/files/tor/run
@@ -1,4 +1,4 @@
#!/bin/sh
[ -r conf ] && . ./conf
-ulimit -n ${MAX_OPEN_FILES:-16384}
+ulimit -n ${MAX_OPEN_FILES:-65536}
exec tor ${OPTS:=--quiet} --runasdaemon 0 2>&1
diff --git a/srcpkgs/tor/template b/srcpkgs/tor/template
index 2e3586061d77..5c81c8745fdf 100644
--- a/srcpkgs/tor/template
+++ b/srcpkgs/tor/template
@@ -1,7 +1,7 @@
# Template file for 'tor'
pkgname=tor
version=0.4.7.8
-revision=1
+revision=2
build_style=gnu-configure
configure_args="--enable-zstd"
hostmakedepends="pkg-config"
next reply other threads:[~2022-07-22 9:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 9:18 steinex [this message]
2022-07-23 15:05 ` [PR PATCH] [Merged]: " sgn
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38188@inbox.vuxu.org \
--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).