From owner-freebsd-arch  Tue Jan  9  7:55:14 2001
Delivered-To: freebsd-arch@freebsd.org
Received: from spirit.jaded.net (shortbus.jaded.net [216.94.132.8])
	by hub.freebsd.org (Postfix) with ESMTP
	id 6D9CB37B6A8; Tue,  9 Jan 2001 07:54:57 -0800 (PST)
Received: (from dan@localhost)
	by spirit.jaded.net (8.11.1/8.11.1) id f09Fsk300463;
	Tue, 9 Jan 2001 10:54:46 -0500 (EST)
	(envelope-from dan)
Date: Tue, 9 Jan 2001 10:54:45 -0500
From: Dan Moschuk <dan@freebsd.org>
To: arch@freebsd.org
Cc: markm@freebsd.org
Subject: Keeping an /entropy file
Message-ID: <20010109105445.A434@spirit.jaded.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
Sender: owner-freebsd-arch@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Hi everyone, I hope everyone enjoyed (or is still enjoying) their holidays.

Without too big of a bikeshed, what does everyone think of either 
adding a system crontab or modifying the random device itself to generate
/entropy at a specified interval?  If the system crashes and doesn't get
a chance to shut itself down properly, the next bootup can be somewhat slow
(especially if there's no keyboard to mash on).  This is especially
relevant on servers.

Cheers!
-dan
-- 
Man is a rational animal who always loses his temper when he is called
upon to act in accordance with the dictates of reason.
                -- Oscar Wilde


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message