Hi Pieter, On Sat, Nov 25, 2017 at 04:07:23PM +0100, PiBa-NL wrote: > Personally i do not need master-worker at present time..
OK, that's better for us now :-) > But running it with 'quiet' configuration option or -q startup parameter is > something that imho does need to be checked though. It seems to always die > when doing so after sending a USR2, also without using daemon mode.!. (i > didn't quite specify that fully in the other mail/thread..) I can't reproduce this one either. It may be related to the other issue. We'll have to check why the master-worker model works so differently on FreeBSD. It may be a small mistake somewhere or something behaving differently that we have overlooked. But clearly the issue with listening FDs not responding after the fork is *very* strange and I suspect it's only the visible part of something misbehaving. > -- Some background info -- > My usecase mainly revolves around running haproxy on pfSense (a FreeBSD > firewall distribution), im using and maintaining the haproxy 'package' for > it. > All services there are 'managed' by php and shell scripts. When users modify > the configuration in the webgui and press 'apply' i need to restart haproxy > and show any warnings/alerts that might have been returned. > This has worked and still works fine without requiring master-worker. Thanks for the heads-up, now I understand better you use case. > So no problem or missing advantages for myself or users of that package if > haproxy 1.8 gets released as it currently is. Great. > I'm not sure if other folks are using some service management tool like > systemd on FreeBSD... For now I don't think so. And I wish them to stay on something sane for as long as they can! > But i guess time will tell, i'm sure 1.8 wont be the > last release ever so fixes when required will come :). Yep, that's the idea! Thanks! Willy
