From owner-freebsd-hackers Thu Apr 19 13: 6:45 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from winston.osd.bsdi.com (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id EB30A37B423 for ; Thu, 19 Apr 2001 13:06:42 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.3/8.11.2) with ESMTP id f3JK6UM81411; Thu, 19 Apr 2001 13:06:30 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) To: dp@penix.org Cc: hackers@FreeBSD.ORG Subject: Re: Dilemma. In-Reply-To: <3ADF04E8.55D0888E@penix.org> References: <3ADF04E8.55D0888E@penix.org> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010419130630B.jkh@osd.bsdi.com> Date: Thu, 19 Apr 2001 13:06:30 -0700 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 11 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You probably want to use the soft updates "snapshot" mechanism to take a frozen snapshot of the filesystem state and then run your checksumming/fingerprinting scan on that. At that point it's obviously going to be divergent with the ongoing state of the filesystem if that filesystem is active, but such is generally true of any monitoring mechanism, you just want to make sure that the state doesn't change under you as you're trying to derive your "base delta" state. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message