From owner-freebsd-bugs Fri Feb 25 8: 0:11 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 2B0B637C3A5 for ; Fri, 25 Feb 2000 08:00:04 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id IAA57109; Fri, 25 Feb 2000 08:00:03 -0800 (PST) (envelope-from gnats@FreeBSD.org) Date: Fri, 25 Feb 2000 08:00:03 -0800 (PST) Message-Id: <200002251600.IAA57109@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Panagiotis Christias Subject: Re: kern/16568: How to crash FreeBSD 4.4 Reply-To: Panagiotis Christias Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/16568; it has been noted by GNATS. From: Panagiotis Christias To: freebsd-gnats-submit@FreeBSD.org, bg@bg.sics.se Cc: Subject: Re: kern/16568: How to crash FreeBSD 4.4 Date: Fri, 25 Feb 2000 17:51:25 +0200 Hello, this is yet another report, this bug was responsible for crashing your four brand new cache boxes for the past 25 days during peak time, running FreeBSD-3.4STABLE(?) and the latest Squid (2.2STABLE5). Since installing the patch (4 days ago) all systems all running smoothly without any problem. I strongly suggest that you add the patch as soon as possible to the 3.0-stable branch. I'ld be surprised if this bug is responsible for several other crashes, like the kern/16890 case... Regards, Panagiotis, crash no more! -- Panagiotis J. Christias Network Management Center P.Christias@noc.ntua.gr National Technical Univ. of Athens, GREECE To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message