Re: upstream member liveness

2016-04-13 Thread B.R.
Waow. I am off-topic, but Valentin I shall note you are showing a great deal of patience. Without any doubt your interlocutor will be glad and thankful for it, and will demonstrate it as good as when he (quickly) becomes upset. Btw, I do not know any Captain Evidence, only Captain Obvious. ---

Re: upstream member liveness

2016-04-13 Thread Валентин Бартенев
On Wednesday 13 April 2016 00:47:14 drookie wrote: > Is there someone besides Captain Evidence who knows the answer ? This is > actually the problem of the modern internet: half of the decent questions is > flooded out by people, who not only think they know the answer, but are > arrogant enough

Re: upstream member liveness

2016-04-13 Thread Francis Daly
On Wed, Apr 13, 2016 at 12:47:14AM -0400, drookie wrote: Hi there, > Is there someone besides Captain Evidence who knows the answer ? There's you, me, him, them, everybody. At least, everybody who read the previous answers in the thread. > This is > actually the problem of the modern

Re: upstream member liveness

2016-04-12 Thread drookie
Is there someone besides Captain Evidence who knows the answer ? This is actually the problem of the modern internet: half of the decent questions is flooded out by people, who not only think they know the answer, but are arrogant enough to insist it, and from the point of an outer observer the

upstream member liveness

2016-04-11 Thread drookie
What is the scope of the upstream member liveness: is it per upstream group, or per vhost ? If the question is unclear, consider I have 3 nginx - one balancer and two backends, and the following config part on the nginx balancer: upstream backends { server 192.168.0.1; server