My experience is not good. With sf and st duplicated and created children process for any reload.
With st lost pid and zombie process make. With sf and st so much conections in state CLOSE WAIT. El 07/04/2014 16:30, "Patrick Viet" <patrick.v...@gmail.com> escribió: > Hi, > > I'm wondering if there is some way to have some kind of timeout after > haproxy receives the USR1 soft stop signal sent by haproxy -sf <old > process>. I don't want to kill everyone brutally, but if I have a client > that's hanging on for a connection way too long after a reconfiguration, > may he die!! For now I'm thinking about something that sends a TERM after > an hour or so, but there might be something that's a bit cleaner. > > Didn't find anything in the docs. Or am I looking badly? > > Hints? Experience? Ideas? > > Thanks! > > Patrick >
