Re: [squid-users] Upgrading to Squid 2.4

There's a bug in the cersion of gcc shipped on openBSD that squid'
configure doesn't detect. Rebuild lib/* with -O not -O2, and then relink
the main squid file.

Rob

----- Original Message -----
From: "Nigel Punton" <nigelp@dolfin.com>
To: <squid-users@squid-cache.org>
Sent: Saturday, March 24, 2001 3:08 AM
Subject: [squid-users] Upgrading to Squid 2.4

>
> I am using OpenBSD 2.8 and have been using squid 2.3 successfully for
quite
> some time, with the redirection program squidGuard.
>
> I recently undertook the challenge of upgrading to 2.4stable. I have
it up
> and running in it's new directory of /usr/local/squid/bin. After
playing
> around with directory ownership
>
> drw-rw-rw- 2 nobody nobody 512 Mar 6 12:57 bin
> drw-rw-rw- 18 nobody nobody 512 Mar 6 15:40 cache
> drw-rw-rw- 4 nobody nobody 512 Mar 6 12:57 etc
> drw-rw-rw- 3 nobody nobody 512 Mar 6 11:52 libexec
> drw-rw-rw- 2 nobody nobody 512 Mar 6 16:42 logs
>
> I was able to run the squid -z and eventually squid. The problem is
> whenever a site is accessed it kills the child process and restarts
squid.
> Error message show something like this:
> squid[12449] Squid parent: child process 10398 exited with status 0
>
> I have tried it on three different OpenBSD boxes all with the same
results,
> Can anyone tell me what files squid need to access while running and
which
> service needs to own these files?
> My gut feeling is this is a rights or ownership issue.
>
> Any help would be greatly appreciated.
>
> nigel
>
>
Received on Fri Mar 23 2001 - 15:41:12 MST