I was wondering if Pound supports the creation of a group of backend servers. 
Say I've got a pound server that support 20 websites (unique public IP's / SSL
certs) but I use the same 10 web servers.  Is there a way to avoid having to
list the backend servers for each of the 20 websites?

Thanks,
Adam

Adam Landry wrote:
> I was wondering if Pound supports the creation of a group of backend
> servers.  Say I've got a pound server that support 20 websites
> (unique public IP's / SSL certs) but I use the same 10 web servers.
> Is there a way to avoid having to list the backend servers for each
> of the 20 websites?

They're not explicitly named "pools", nor are they as formal as you 
describe, but its possible and easy.

Take the following snippit for example:

ListenHTTP
         Address 127.0.0.1
         Port 80
End
ListenHTTP
         Address 127.0.0.2
         Port 80
End
ListenHTTP
         Address 127.0.0.3
         Port 80
End
Service "default"
	Backend
		Address 192.168.1.1
		Port 80
	End
	Backend
		Address 192.168.1.2
		Port 80
	End
	Backend
		Address 192.168.1.3
		Port 80
	End
End

In this example incoming traffic to 127.0.0.{1,2,3} would all be served 
by the group of backends in the "default" service directive.

Pound uses a first-match system, so just put the "default" block last in 
your cfg file and make sure nothing else matches it.

The above may not be 100% ideal, since you may have to repeat yourself a 
little in places, but perl or whatever your favorite scripting language 
is helps there.


-- 
Dave Steinberg
http://www.geekisp.com/
http://www.steinbergcomputing.com/