Bug 1299972 - squid file descriptor limit hardcoded to 16384 via compile option in spec file
Summary: squid file descriptor limit hardcoded to 16384 via compile option in spec file
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: squid
Version: 7.2
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Luboš Uhliarik
QA Contact: Martin Frodl
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-19 16:04 UTC by Walter Haidinger
Modified: 2019-11-14 07:20 UTC (History)
3 users (show)

Fixed In Version: squid-3.5.10-1.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-03 21:16:48 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:2600 0 normal SHIPPED_LIVE Moderate: squid security, bug fix, and enhancement update 2016-11-03 12:12:25 UTC

Description Walter Haidinger 2016-01-19 16:04:12 UTC 
Description of problem:
The number of file descriptiors used by squid is hardcoded to 16384 via a compile option in the spec file.
  182:     --with-filedescriptors=16384 \

This prevents raising the FD limit with e.g. LimitNOFILE in systemd's squid.service file. 

Version-Release number of selected component (if applicable):
squid-3.3.8-26.el7

How reproducible:
always

Steps to Reproduce:
1. add LimitNOFILE=32768 to [Service] section in squid.service
2. restart squid
3. check "open files" in /proc/<pid>/limits or squid's cache.log:

Actual results:
Max. number of open file descriptors still 16384.

Expected results:
LimitNOFILE directive honored

Additional info:
Duplicate of: https://bugzilla.redhat.com/show_bug.cgi?id=976815
Comment 7 errata-xmlrpc 2016-11-03 21:16:48 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2016-2600.html
Note You need to log in before you can comment on or make changes to this bug.