2009/1/15 Mark Powell m.s.pow...@salford.ac.uk:
Did you manage to get that FreeBSD 7 server working with COSS?
Well did you :)
Yes. At least in testing. I don't (yet) have a client running
FreeBSD-7 and using COSS.
This problem still exists in the latest squid. Any likelihood of a fix, or
On Wed, 1 Oct 2008, Mark Powell wrote:
On Fri, 12 Sep 2008, Adrian Chadd wrote:
Well, I fixed the thing up under FreeBSD so it certainly was working
for me at some point.
I'm one server away from getting my polygraph test cluster going and
I'll hopefully be installing that tomorrow; I'll
On Fri, 12 Sep 2008, Adrian Chadd wrote:
Well, I fixed the thing up under FreeBSD so it certainly was working
for me at some point.
I'm one server away from getting my polygraph test cluster going and
I'll hopefully be installing that tomorrow; I'll make sure COSS gets a
decent thrashing when
On Fri, 12 Sep 2008, Amos Jeffries wrote:
Can you report a bug on this please, so we don't forget it. with a stack
trace when the crash is occuring.
Already did, last year:
http://www.squid-cache.org/bugs/show_bug.cgi?id=1944
Does this mean that COSS can't be successfully used with FreeBSD
Well, I fixed the thing up under FreeBSD so it certainly was working
for me at some point.
I'm one server away from getting my polygraph test cluster going and
I'll hopefully be installing that tomorrow; I'll make sure COSS gets a
decent thrashing when thats all up and running.
adrian
On Thu, 14 Aug 2008, Mark Powell wrote:
On Thu, 14 Aug 2008, Adrian Chadd wrote:
Don't load aio.ko; that way if squid tries using the POSIX AIO
routines it'll crash.
I should get around to removing those from Squid-2.HEAD (as the
implementation isn't good enough for the current way Squid does
Mark Powell wrote:
On Thu, 14 Aug 2008, Mark Powell wrote:
On Thu, 14 Aug 2008, Adrian Chadd wrote:
Don't load aio.ko; that way if squid tries using the POSIX AIO
routines it'll crash.
I should get around to removing those from Squid-2.HEAD (as the
implementation isn't good enough for the
On Thu, 26 Apr 2007, Adrian Chadd wrote:
Change:
xmemcpy(p, buf, len);
to be:
if (errflag == 0) {
assert(len = 0);
xmemcpy(p, buf, len);
}
That should stop the crashes but it won't stop the IO errors and I'm not
quite sure whether COSS will return crap to the client request or not.
COSS
On Thu, Apr 26, 2007, Mark Powell wrote:
It does stop the crashes, but I'm getting a lot of errors, so of which
appear to be new ones:
Very eww. Now we need to figure out why the hell its spitting out those pending
relocate
IO errors as its probably playing havoc with things.
Could you do
