Yes but the day before i was running an earlier version of FreeBSD
version 2.2.2-RELEASE which i used without any problem at all for the last 8
months or so. The machine stayed up for the last 6 months without a hicup
This problem has only manifested since upgrading
Michael
-----Original Message-----
From: Daniel Kiracofe <drk@gurulink.com>
To: Michael Slater <mikey@iexpress.net.au>
Cc: squid-users@nlanr.net <squid-users@nlanr.net>
Date: Tuesday, March 24, 1998 1:37 PM
Subject: Re: Squid Logs
>On Tue, 24 Mar 1998, Michael Slater wrote:
>> After setting up a machine Running FreeBSD 2.2.5-RELEASE and
>> installing squid 1.1.20, i have started seing the following errors. The
>> machine in question is a Pentium Pro, with 256 mb of ram, and 9.2 gigs of
>> swap space. The folowing keeps apearing in the output of "dmesg"
>>
>> > pid 157 (squid), uid 65534: exited on signal 6
>> > pid 271 (squid), uid 65534: exited on signal 6
>
> IIRC, signal 6 is IOT/abort and is usually indicative of bad hardware
>(just like the infamous signal 11). You probably have a couple of bad
>megs in that 256 Megs. My experience is mostly w/ linux, so there may be
>FreeBSD specific reasons for this signal that I'm overlooking, but I'd say
>checking the ram would be a good starting point...
>
>/* Daniel */
>WWW: http://users.gurulink.com/drk
>Linux Consultation Specializing in TCP/IP Networking and Web Caching
>
>"Fear is only afraid of the absence of itself" - Mediocrates
>
>
Received on Mon Mar 23 1998 - 22:09:27 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:39:26 MST