Launchpad has imported 4 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=976815.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2013-06-21T14:16:56+00:00 Zing wrote: Version-Release number of selected component (if applicable): squid-3.2.9-1.fc18.x86_64 It's not possible to change the number of file descriptors available to squid at runtime with either the "max_filedescriptors" option or by specifying the open files limit in systemd squid unit file. Attempting to use max_filedescriptors option gets an error: WARNING: max_filedescriptors disabled. Operating System setrlimit(RLIMIT_NOFILE) is missing. Rebuilding squid without the "--with-filedescriptors=16384" option in the spec file causes squid to inherit the build environments open files limit as its default (i.e. 1024 as a user), but the squid unit file option "LimitNOFILE=16384" is now obeyed and set if systemd is used to start squid. The max_filedescriptor option also starts working at this point. Can we get squid built without the "--with-filedescriptors=16384" build option. Thank you. Reply at: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1390132/comments/0 ------------------------------------------------------------------------ On 2013-06-24T17:34:36+00:00 Michal wrote: It would make sense to compile squid without the file descriptors limit and treat systemd LimitNOFILE as a boundary for config value, but there is an issue when squid.conf value is higher than LimitNOFILE. In this case squid logs and probably also uses max_filedescriptor value instead of current fd limit. I will initiate discussion with upstream on the theme of systemd and squid. Reply at: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1390132/comments/1 ------------------------------------------------------------------------ On 2013-06-24T20:23:10+00:00 Zing wrote: Yes. From my testing (with a squid built without the --with- filedescriptors option), if max_filedescriptors is not set, squid will just inherit the current rlimit setting of nofile (I made an error in my comment 0, it does not come from the build environment). If max_filedescriptors is set, then that is what squid will use, regardless of the nofile rlimit. Is that necessarily an issue? That seems "ok" to me and the effect I'd want (being able to "override" the rlimit in the squid config). The only kind of maybe unexpected thing here is if one doesn't use systemd to start squid, the default squid configuration is probably going to inherit a filedescriptor limit much smaller (1024) than the systemd LimitNOFILE specified 16384. Reply at: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1390132/comments/2 ------------------------------------------------------------------------ On 2013-09-13T11:20:51+00:00 Michal wrote: You can find the newest Squid build without "--with-filedescriptors" option in rawhide. Reply at: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1390132/comments/3 ** Changed in: squid3 (Fedora) Status: Unknown => Fix Released ** Changed in: squid3 (Fedora) Importance: Unknown => Undecided -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1390132 Title: Cannot change the maximum number of filedescriptors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1390132/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
