From owner-freebsd-hackers Wed Oct 27 10:38: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gw0.boostworks.com (gw0.boostworks.com [194.167.81.213]) by hub.freebsd.org (Postfix) with ESMTP id C616314FA6 for ; Wed, 27 Oct 1999 10:37:50 -0700 (PDT) (envelope-from root@synx.com) Received: from synx.com (root@rn.synx.com [192.1.1.241]) by gw0.boostworks.com (8.9.1/8.9.1) with ESMTP id TAA74470 for ; Wed, 27 Oct 1999 19:39:31 +0200 (CEST) Message-Id: <199910271739.TAA74470@gw0.boostworks.com> Date: Wed, 27 Oct 1999 19:37:11 +0200 (CEST) From: Remy Nonnenmacher Reply-To: remy@synx.com Subject: Running unattended (ifo FFS thread) To: hackers@freebsd.org MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In followup of the FFS thread, I would like to know if there are some recommendations for running unattended machines. For exemple, avoiding the 'run fsck manually' (for exemple, when co-locating a machine far away where it is not possible to get a console login). Hints appreciated on other points that may lead to human intervention and how to avoid it. Thanks, RN. ItM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message