RE: Bad performance

>But.. if you have config like this:
>     echo "http://0.0.0.0:8080" > /proc/net/tux/0/listen/0
>     echo "8080" > /proc/sys/net/tux/clientport
>
>You can expect troubles....
>Tux was trying to forward every 404 to itself, and that created an infinite
>loop of requests to itself, which explains the high CPU load and the
>increase in time.

Wow, nice debugging job!

I bet this was the same problem I had months ago, though, I "fixed" it by 
moving it to an alternate IP/port (that didn't use 8080, thus no looping).

I never wanted to use the clientport stuff, I just wanted an separate 
standalone server.  So I ignored it in the config, thinking it wouldn't 
matter.  I never considered that tux might call itself back on the port it 
was running on and loop.

Seems like something that could be fixed in the code.  If clientport = 
myport, don't forward.

-bill