e2guardian does not start out-of-the-box on armhf because "On 32-bit systems reduce this to 300 to avoid exceeding the <4GB virtual memory limit"
Bug #2037958 reported by
Steve Langasek
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| e2guardian (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Bug Description
/etc/e2guardian
# This figure is the maximum number of concurrent connections.
# If more connections are made, connections will queue until a worker thread is free.
# On large site you might want to try 5000 (max value 20000)
# 500 is the default suitable for home or samll office use on 64-bit systems
# On 32-bit systems reduce this to 300 to avoid exceeding the <4GB
# virtual memory limit and on Linux decrease the thread stack size from
# 10MB to 2MB (ulimit -s 2048)
httpworkers = 500
It shouldn't tell users to reduce the limit on 32-bit archs. It should just be reduced in the package on 32-bit archs.
| summary: |
- "On 32-bit systems reduce this to 300 to avoid exceeding the <4GB - virtual memory limit" + e2guardian does not start out-of-the-box on armhf because "On 32-bit + systems reduce this to 300 to avoid exceeding the <4GB virtual memory + limit" |
| Changed in e2guardian (Ubuntu): | |
| importance: | Undecided → High |
| status: | New → Triaged |
| Changed in e2guardian (Ubuntu): | |
| status: | Triaged → Fix Committed |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in e2guardian (Ubuntu): | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
This bug was fixed in the package e2guardian - 5.3.5-4.1ubuntu1
---------------
e2guardian (5.3.5-4.1ubuntu1) mantic; urgency=medium
* debian/
correct worker count on 32-bit archs. Closes LP: #2037958.
-- Steve Langasek <email address hidden> Mon, 02 Oct 2023 00:33:54 -0700