I'm on Linux so I think that /etc/security/limits.d and /etc/security/limits.conf are where I would change the default settings for a user - however the ulimit-n setting in haproxy is a fraction of what the user's current ulimit -n is, and I'm not sure why.
On Sat, Apr 2, 2016 at 4:46 PM, PiBa-NL <[email protected]> wrote: > Op 2-4-2016 om 22:32 schreef CJ Ess: > > So in my config file I have: > > maxconn 65535 > fullconn 64511 > > However, "show info" still has a maxconn 2000 limit and that caused a blow > up because I exceeded the limit =( > > So my questions are 1) is there a way to raise maxconn without restarting > haproxy with the -P parameter (can I add -P when I do a reload?) 2) Are > there any other related gotchas I need to take care of? > > I notice that ulimit-n and maxsock both show 4495 despite "ulimit -n" for > the user showing 65536 (which is probably half of what I really want since > each "session" is going to consume two sockets) > > as for ulimit-n on freebsd i need to set these two system flags: kern.maxfiles > kern.maxfilesperproc what OS are you using? > > > I'm using haproxy 1.5.12 > > >
