Hi Cyril, On Tue, Dec 14, 2010 at 12:34:13AM +0100, Cyril Bonté wrote: > Hi Willy, > > Seeing some issues in the mailing list with the couple appsession/nbproc > 1, > I'm working on a small patch to add some warnings if appsession or sticking > rules are used on multiple processes (I leave them as non fatal errors to not > break current configurations).
good idea ! > I've not tested peers yet, but I wonder if there won't be some huge issues > with nbproc > 1 in that case too. This is a good point. In my opinion, each process' connection will cause the other one to be dropped, and no process will manage to keep a connection established. > I see at least 2 possibilities to prevent those issues : > - the simplest, by adding a fatal error if peers are used with nbproc > 1 > - add a facultative "bind-process" on each "peer" line, which can take one > and > only one process-number. > > There are maybe some other (and better) solutions, discussion is opened ;-) Option 1 is by far the best one for now. Later we'll see how we can make several processes issued from the one communicate together and/or to other processes. Since it's not the goal right now, I like the fatal error, it will save a lot of headaches to some admins who don't necessarily check the warnings. Thanks! Willy
