/ Zope / Apsis / Pound Mailing List / Archive / 2005 / 2005-07 / --version?

[ << ] [ >> ]

[ pound and SSL wildcard certs [scanned] / Veit ... ] [ Silence / James Billson <james.billson(at)cim.c... ]

--version?
Ximon Eighteen <ximon.eighteen(at)int.greenpeace.org>
2005-07-07 17:20:29 [ FULL ]
Hi all,

What's the "correct" way to determine the version of a pound binary installed 
on a system?

The man page says -f only is the only recognised command line option in my 
version. I tried using strings on the binary and found this:

$Id: pound.c,v 1.7 2004/03/24 06:59:59 roseg Rel $

So I assume I have v1.7 of Pound, sounds about right given the latest version 
is 1.9.

I checked the man page for 1.9 and that lists more command line options but 
still no means of determining the version. I searched this mailing list for 
"find version", "determine version", "version", "which version" etc. but 
didn't turn up anything useful in my (brief) search.

Am I missing something here?

X

Re: --version?
Ximon Eighteen <ximon.eighteen(at)int.greenpeace.org>
2005-07-07 17:25:08 [ FULL ]
Hi again,

On a related note would it be asking too much for pound to object to bad 
command line arguments and quit instead of ignoring them silently and 
running?

I invoked pound with -V, -v and --version and ended up with three running 
copies, annoying on a test system and a problem if (note: I wouldn't execute 
pound without knowing the consequences) run on a production system could be 
more of a problem (though I suppose the real running pound instance has 
already bound to any ports it needs, though if pound were deliberately not 
running it could be annoying to have it start when that wasn't what you 
intended).

Even --help causes it to run.

Note I checked v1.9 and the same behaviour still occurs as in my version.

X

MailBoxer