From owner-freebsd-stable Wed Aug 23 22: 3: 0 2000 Delivered-To: freebsd-stable@freebsd.org Received: from sanson.reyes.somos.net (freyes.static.inch.com [216.223.199.224]) by hub.freebsd.org (Postfix) with ESMTP id 475BD37B423 for ; Wed, 23 Aug 2000 22:02:57 -0700 (PDT) Received: from tomasa (tomasa.reyes.somos.net [10.0.0.11]) by sanson.reyes.somos.net (8.9.3/8.9.3) with SMTP id AAA31598 for ; Thu, 24 Aug 2000 00:54:26 -0400 (EDT) (envelope-from fran@reyes.somos.net) Message-Id: <200008240454.AAA31598@sanson.reyes.somos.net> From: "Francisco Reyes" To: "FreeBSD Stable List" Date: Thu, 24 Aug 2000 01:03:50 -0400 Reply-To: "Francisco Reyes" X-Mailer: PMMail 2000 Professional (2.10.2010) For Windows 98 (4.10.2222) MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Subject: Upcoming rc.conf changes not loading certain currently loaded daemons Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On a recent email Peter Jeremy wrote: >..., rc.conf was recently changed (in -current) to not >start inetd, portmap or sendmail. If you are actually relying on >any of these daemons, and you actually notice the differences in >/etc/defaults/rc.conf, you will be able to update /etc/rc.conf >without a period of head-scratching when they don't start. What was the reason for these daemons been set to not start? Wouldn't this "break" working machines? francisco Moderator of the Corporate BSD list http://www.egroups.com/group/BSD_Corporate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message