From owner-freebsd-security Mon Nov 24 20:30:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA08667 for security-outgoing; Mon, 24 Nov 1997 20:30:19 -0800 (PST) (envelope-from owner-freebsd-security) Received: from clipper.ua.net (root@smtp1-1.ua.net [195.5.14.40]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id UAA08662 for ; Mon, 24 Nov 1997 20:30:14 -0800 (PST) (envelope-from daemon@bit.cs.kiev.ua) Received: from bit.cs.kiev.ua ([193.124.54.47]) by clipper.ua.net with smtp id m0xaCdR-000sytC; Tue, 25 Nov 97 06:30 WET Apparently-To: Received: (from daemon@localhost) by bit.cs.kiev.ua (8.7.5/8.6.9) id GAA20049 for security@freebsd.org; Tue, 25 Nov 1997 06:30:09 +0200 (EET) Date: Tue, 25 Nov 1997 06:30:09 +0200 (EET) From: Owner of many system processes Message-Id: <199711250430.GAA20049@bit.cs.kiev.ua> Sender: owner-freebsd-security@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Alexander Litvin (archer@lucky.net) wrote: > Hi! > Until now, I was unable to freeze any of our FreeBSDs -- > 2.2.1, 2.2.2, 2.2.5-STABLE (about two weeks, no fix), > 3.0-CURRENT (about the beginning of November). I second this. I have 2.2.5 (makeworlded), 2.2-stable which is a bit earlier than that, couple of old 2.2s (all older than 2.2-RELEASE), and 3.0-971008-SNAP. None of them crashed (and some non-freebsd boxes crashed, so I am sure it is the right kind of code). all the hosts in question have IPFIREWALL in kernel; probably by incident ;-) -- There is no human problem which could not be solved if people would simply do as I advise. -Gore Vidal