Hi;
I'm confused by the man page. It states that I can add:
* LogLevel x // where x is a number between 1 and 4 to the ListenHTTP 
container
* TimeOut // to the Service container (but doesn't tell me the 
format...is it "30" or "30 sec" 04 "30s"???
* TTS // to the Service container (same problem as above)
However, whenever I add any of those, pound won't restart. The 
/var/log/messages showed that it didn't like the LogLevel (unknown 
directive). So what gives? Are all these things obsolete? What do I use? 
What documentation should I follow if not the man page?
TIA.
beno

Mon, Aug 14, 2006 ve 01:55:57PM -0400, zope(at)2012.vi napsal:[...]

LogLevel 0
TimeOut 120

etc..

But you need to enter them to right sections...

--
 .''`. Ondra 'Kepi' Kudlik
: :' : Debian GNU/Linux User
`. `'
  `-   http://www.nosoftwarepatents.com/cz/m/intro/index.html


[...]

Ondra Kudlik wrote:[...]
Googling gave me this which worked ;)

LogLevel     2
ListenHTTP
 Client 120
 Address 202.71.106.119
 Port    80
  Service
   HeadRequire "Host: .*mrtablecloth-vi.com.*"
    BackEnd
    Address 202.71.106.119
    Port    8080
    TimeOut 30
   End
  End
 End
End

That's a snip of a long pound.cfg file that details out every URL 
specifically. I had a catch-all at the bottom like this:

  Service
   BackEnd
   Address 202.71.106.119
   Port    81
  End

where port 81 would be my yet-to-be configured squid cache proxy. 
Interestingly, I noticed this in /var/log/messages after the client 
tried unsuccessfully to hit the site:

Aug 14 18:34:21 server167 pound: backend 202.71.106.119:81 connect: 
Connection refused

which seems to indicate that Pound did *not* transfer the request to 
port 8080 (a Zope instance). However, I can hit the site with no 
problems, and the client reports a "Welcome to Web.vi \n Zope" where 
web.vi is my personal site and name of the server (localhost.web.vi) and 
also resolves for me. So I'm confused as to where the problem is...in 
Pound, or in Zope...and what it is.

I also noticed this in my log:

Aug 14 18:34:21 server167 pound: no back-end "GET 
/1280/s/c/x/en-us/index.pt HTTP/1.1" from 66.176.146.174
Aug 14 18:34:22 server167 pound: no back-end "GET /favicon.ico HTTP/1.1" 
from 66.176.146.174

which is a comcast IP address, telling me nothing ;) But the "no 
back-end" argument is interesting. This was after the client tried to 
hit the site after before my discovering the port 81 issue. It is 
statistically probable that no other requests came to the box in the 
interval. After I changed the port to 8080, there were no complaints in 
the log, even after the client tried to hit the site again. Ideas as to 
how to proceed?
TIA,
beno