Michael, Run pound with -v to give you output to the console. You can also check your configuration by using -c. For testing, feed the configuration file manually, rather than using a start script. So check the file like this:
pound -v -c -f /etc/pound.cfg (if that is where your configuration file is at). If it doesn't start, it should explain why. If your configuration passes, start pound using: pound -v -f /etc/pound.cfg. As far as your configuration file, I would simplify it until you get it started and configured. Remove the LogFacility unless you have checked your syslog.h file and know for sure you're identifying it correctly. Make sure the user/group exists. Basically remove everything you don't need to specify because its a default and then start adding them back and testing as you do. Rob On Mon, Jul 23, 2012 at 12:11 AM, Michael Miller < [email protected]> wrote: > Sorry correction I do have the .s and *s > >> >> User "michael" >> Group "michael" >> LogFacility daemon >> LogLevel 4 >> Alive 30 >> Client 10 >> TimeOut 10 >> Grace 10 >> >> ListenHTTP >> Address 192.168.1.71 >> Port 8080 >> >> Service >> HeadRequire "Host: .*hostname.dyndns.org.*" >> BackEnd >> Address 192.168.1.72 >> Port 8080 >> End >> End >> End >> >> >> >> >> >> On 7/22/2012 1:45 PM, Dave Steinberg wrote: >> >>> "Some people asked about the possibility of redirecting requests to >>>> back-ends as per some virtual hosts definition. While I believe this is >>>> not /Pound/'s job, it can be done." >>>> >>>> Is pound not the best solution for this? Is there something better? >>>> >>> >>> That is more of an aside than anything else. I suspect that the >>> majority of pound users are doing vhosting based on the Host header as the >>> docs suggest. >>> >>> Bottom line - it works fine, don't let that comment hold you back. >>> >>> Regards, >>> >> >> > > -- > To unsubscribe send an email with subject unsubscribe to [email protected]. > Please contact [email protected] for questions. >
