I know you guys are as frustrated as I am with this, and I really 
appreciate your help. When all else fails, start over from scratch. I 
d/l'd the latest port (a newer one than last week's) and ran:
./configure --with-ssl=/usr/local
make
make install

without a hitch. But once again, when I went to
pound start
it didn't. And it keeps throwing these "unknown extra arguments":
server167# fgrep pound /var/log/messages
Aug  7 16:08:28 server167 pound: starting...
Aug  7 16:08:31 server167 pound: unknown extra arguments (start...)
Aug  7 16:10:43 server167 pound: starting...
Aug  7 16:10:46 server167 pound: unknown extra arguments (start...)
Aug  7 17:23:51 server167 pound: starting...
Aug  7 17:23:54 server167 pound: unknown extra arguments (start...)
Aug  7 17:25:33 server167 pound: starting...
Aug  7 17:25:35 server167 pound: unknown extra arguments (start...)

Why is that? Pound started before just fine. What could possibly have 
changed?? All I've done server-side is work on this issue today...Is it 
possibly trying to start from the old version? How do I stop that?

Once again, here's the pound.cfg file:

ListenHTTP
  Address 0.0.0.0
  Port    80
            Service
                 TimeOut 30
                 BackEnd
                     Address 202.71.106.119
                     Port    8080
                 End
             End
End

Where could the problem be?
TIA,
beno

beno schrieb:
[...]

Once again my question: how do you start pound? What are you typing on
the cli or what is your start/stop-file like?

Regards,

Falk

On Mon, Aug 07, 2006 at 01:33:21PM -0400, beno wrote:[...]

You should try starting pound without the extra command line argument that
it doesn't understand. In other words, start pound by running:

    pound

Instead of:

    pound start

Hope this helps,
Eric