Thanks for the reply Joe.  I'll take a look at your code.

I'm already using a unified include file as was pretty obvious in my snippet:

Include "/etc/pound/vhosts.cfg"


I needed some way to use "*.cfg" or something, since I would prefer to put vhost definitions on separate files.

- Romar




On Friday, 14 January, 2011 10:30 PM, Joe Gooch wrote:
My patch at 
https://users.k12system.com/mrwizard/pound/pound-2.5-03_IncludeDirDirective.patch.bz2
 implements the ability to include multiple files from a directory.  You'd have 
to compile your own pound to use it.

Or, you can modify your startup script to create a unified include file... for 
instance:
/etc/pound/pound.cfg   Include "/etc/pound/vhosts.cfg"

In your startup script:
cat /etc/pound/vhosts.d/*.cfg>  /etc/pound/vhosts.cfg
pound -f /etc/pound/pound.cfg

or similar.


Joe

-----Original Message-----
From: Romar Mayer Micabalo [mailto:[email protected]] On
Behalf Of [email protected]
Sent: Friday, January 14, 2011 6:22 AM
To: [email protected]
Subject: [Pound Mailing List] Include wildcard

Hi,

I currently have the following snippet in my Pound.cfg:

ListenHTTP
     Address 1.2.3.4
     Port 80
     HeadRemove "X-Forwarded-For"
     Include "/etc/pound/vhosts.cfg"
End

My /etc/pound/vhosts.cfg contains:

Service
HeadRequire "^Host:\s*internal.mydomain.com"
         BackEnd
Address 1.2.3.6
Port 8080
End
End

Is it possible to do 'Include "/etc/pound/*.cfg" ' ? This is so that I
can put the config for specific vhosts on separate files. Although I
have tried this and failed using Pound 2.5. Hopefully there's a way to
include multiple config files.

Thank you in advance for your replies.

Best regards.

- Romar



--
To unsubscribe send an email with subject unsubscribe to
[email protected].
Please contact [email protected] for questions.
--
To unsubscribe send an email with subject unsubscribe to [email protected].
Please contact [email protected] for questions.


--
To unsubscribe send an email with subject unsubscribe to [email protected].
Please contact [email protected] for questions.

Reply via email to