KA-BOOM! Hit MaxConn despite higher setting in config file (6 replies)

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)

I'm using haproxy 1.5.12