On Thu, Apr 11, 2019 at 06:51:59PM +0200, Willy Tarreau wrote: > I'm leaning towards what I'd consider a cleaner and more future-proof > option consisting in deprecating "stats bind-process" in favor of "process" > on the stats line (which binds the listener itself, not the whole frontend) > and emitting a warning at startup time if master-worker + this option are > set together, explaining what to do instead. I think it could be a reasonably > acceptable change for 1.9/2.0 given that the overlap between master-worker > and "stats bind-process" should not be high. > > Would you see any issue with this if the warning gives all the indications > on what to do ?
So just to let you know that after discussing this with William, we might have another solution consisting in moving the master-worker socketpair to a dedicated frontend instead. It looks more future-proof but we need to validate a number of points before engaging that route. Regards, Willy
