Seems right, Kinkie. "ulimit Provides control over the resources available to the shell and to processes started by it". So that's why squid process inherits the configuration made on the initialization script. I assume that doesn't matter which user runs the subprocess. But limits.conf is a PAM feature. As you said, it should configure limits on a system basis, for all users configured. What we are saying is that it does not work at boot time, when squid runs. The configuration on the init script is the only way to make it work. On Sun, Sep 15, 2013 at 4:59 PM, Kinkie <gkinkie@xxxxxxxxx> wrote: > On Sun, Sep 15, 2013 at 2:51 PM, Carlos Defoe <carlosdefoe@xxxxxxxxx> wrote: >> I got the same result as Mohsen. The only thing that worked was adding >> "ulimit -n mynumber" to the init script. >> >> It was weird for me, because the script is run by root, not the squid >> user, and i thought ulimit -n applied only to the current logged in >> user. But I think it applies to any session that will start later. > > Ulimits are inherited by all child processes; lowering them is always > possible, raising them may be an administrator-only action. > bash's manual (man 1 bash) has an informative chapter on ulimit. > Otherwise you may want to check setrlimit(2). > System-wide settings may be set in /etc/security/limits.conf (or > /etc/limits.conf, depending on your distro). Man 5 limits.conf has the > details (at least on my Ubuntu Raring system). > > Kinkie
