mod_proxy: Status-Flags vs. 'Hard-Disabling' for BalancerMembers

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi all!

I have a short question: What ist the advantage of the 'disabled'-flag
in:

	BalancerMember http://1.2.3.5:8080 status=+D route=2

since it would be as easy to disable it with a hash-comment (or strip it
completely):

	#BalancerMember http://1.2.3.5:8080 route=2

Sounds more 'safe' to me ;-). Are there any issues with that? (Caching,
active connections, etc..) What's the difference? Or should I use the
'stopped'-flag in addition?
The backend should be disabled for for example maintaining purposes.

Kind regards:
	Florian Schröder


---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
   "   from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx


[Index of Archives]     [Open SSH Users]     [Linux ACPI]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Squid]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]

  Powered by Linux