From owner-freebsd-stable  Thu Aug 24  1:11:18 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from fingers.noc.uunet.co.za (fingers.noc.uunet.co.za [196.31.1.59])
	by hub.freebsd.org (Postfix) with ESMTP id 6897537B423
	for <freebsd-stable@freebsd.org>; Thu, 24 Aug 2000 01:11:15 -0700 (PDT)
Received: from robh (helo=localhost)
	by fingers.noc.uunet.co.za with local-smtp (Exim 3.13 #1)
	id 13Rs6J-0003YW-00; Thu, 24 Aug 2000 10:11:03 +0200
Date: Thu, 24 Aug 2000 10:11:03 +0200 (SAST)
From: fingers <fingers@fingers.co.za>
X-Sender: robh@fingers.noc.uunet.co.za
To: Francisco Reyes <fran@reyes.somos.net>
Cc: FreeBSD Stable List <freebsd-stable@freebsd.org>
Subject: Re: Upcoming rc.conf changes not loading certain currently loaded daemons
In-Reply-To: <200008240454.AAA31598@sanson.reyes.somos.net>
Message-ID: <Pine.BSF.3.96.1000824101029.510G-100000@fingers.noc.uunet.co.za>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi

> What was the reason for these daemons been set to not start?
> Wouldn't this "break" working machines?

I don't know what percentage of installers are doing the same, but the
first thing I do is disable them and kill 'em dead.

--Rob



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