From owner-freebsd-current Sun Feb 4 8:10:50 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 35BFB37B491; Sun, 4 Feb 2001 08:10:30 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f14GAdB19407; Sun, 4 Feb 2001 17:10:39 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Robert Watson Cc: freebsd-current@FreeBSD.ORG Subject: Re: Reclaim 8 0 Killed In-Reply-To: Your message of "Sun, 04 Feb 2001 11:06:26 EST." Date: Sun, 04 Feb 2001 17:10:38 +0100 Message-ID: <19405.981303038@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It's normal. bpf implements what I currently have for my preferred way of preventing a DoS with cloning devices. The message indicates that the bpf0 device node were reclaimed. Poul-Henning In message , Robert Watson writes: > >Updated to a recent -CURRENT yesterday on one of my boxes, and noticed a >slightly unusual shutdown message: > > syncing disks... 8 8 5 5 1 1 > done > Reclaim 8 0 Killed > Uptime: 10h23m28s > Rebooting... > >Don't know what it means, or if it's harmful, but it's certainly different >:-). > >Robert N M Watson FreeBSD Core Team, TrustedBSD Project >robert@fledge.watson.org NAI Labs, Safeport Network Services > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message