[squid-users] Re: how to determine what ./configure options were used?

Thanks Tony and Colin -

strings squid | grep -i delay does indeed show up the relevant symbols on a
--enable-delay-pools binary.

the config.status of the original compilation confirmed the current
installation was not
compiled with --enable-delay-pools, so I'll have to rebuild.

Now; I take it I can just test my new binary by:
a) stop current squid instance
b) fire delaypools binary up pointing to the new delaypools squid.conf file
c) if it goes pear-shaped, just kill and cut the other one back in

What impact do 'users' generally see on stop/starts - is there a service
interrupt
 or do they just timeout?

not that I'm nervous about it (~quiver~)!

cheers,
Mike

> On Tue, 3 Jul 2001, Mike Kiernan wrote:
>
> > Is there any way to tell what options a squid installation was
> > ./configure'd with?
> > Specifically I want to know whether it was compiled with
> > --enable-delay-pools
> > - if it is I guess I can just edit my delay pool rules in and kill
> > -HUP it.
> > If not, I have to recompile - but in that case I also would like to
> > know what other
> > options it was compiled with previously....?
>
> I'm not sure about this but you could try:
> $ strings `which squid` | grep delay
> file_close: FD %d, delaying close
> (my squid wasn't comiled with delay pools)
>
> I'm guessing that if squid was compiled with support for delay-pools you'd
> see the things like:
> delay_pools
> delay_class
>
> I'm sure the gurus can tell you if I'm wrong.
>
> Yours Tony.
>
> /*
> * "The significant problems we face cannot be solved at the
> * same level of thinking we were at when we created them."
> * --Albert Einstein
> */

> Subject:
> Re: [squid-users] how to determine what ./configure options were used?
> Date:
> Wed, 4 Jul 2001 09:44:56 +1000 (EST)
> From:
> Colin Campbell
> To:
> Mike Kiernan
> CC:
>
>
>
>
>
> Hi,
>
> If yiou still have the directory in which it was compiled, look at
> config.status. If not, it's probably tough bikkies. About all you can do
> is try options that require configuration - if they work there's a fair
> chance it was configured with --something. If it doesn't work, it probably
> wasn't.
>
> On Tue, 3 Jul 2001, Mike Kiernan wrote:
>
> > Is there any way to tell what options a squid installation was
> > ./configure'd with?
>
> Colin
>
>
>
Received on Wed Jul 04 2001 - 05:42:30 MDT