From owner-freebsd-stable Wed Jan 30 2: 1: 1 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mass.dis.org (dhcp45-21.dis.org [216.240.45.21]) by hub.freebsd.org (Postfix) with ESMTP id 5AB0C37B42A for ; Wed, 30 Jan 2002 02:00:41 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.6) with ESMTP id g0UA0Yb01251; Wed, 30 Jan 2002 02:00:37 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200201301000.g0UA0Yb01251@mass.dis.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: "Mike Meyer" Cc: stable@freebsd.org Subject: Re: *_enable="YES" behavior is bogus In-reply-to: Your message of "Tue, 29 Jan 2002 20:19:49 CST." <15447.22597.666281.179771@guru.mired.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 30 Jan 2002 02:00:34 -0800 From: Michael Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > If you build a kernel without INET, the following switches don't > result in any daemons being started if you set them to YES: > > syslog_enable > sendmail_enable > lpd_enable I think you are confused. These will all start regardless of whether INET is enabled. > These are all things that are clearly useful on a system without an > internet connection. None of them start if you disable INET in the > kernel. Neither the defaults/rc.conf file, the rc.conf man page, nor > the man pages for those daemons mentiont that INET is required in the > kernel to run them. Nor do the LINT or GENERIC files mention that > turning off INET will cause various daemons useful on a machine > without an internet connection to quit working. You seem surprised that programs which depend upon networking don't function as expected when it is not available. > If anyone is actually willing to > look at fixing these things, I'll PR them. And probably start a > witchhunt for other rc.conf variables that can be broken by careful > selection of options in the config file. Why not fix them yourself? The issues you're observing have nothing to do with rc.conf variables; they have to do with bugs in the above-referenced programs, specifically, they depend upon networking. > So simply > expanding the documentation and comments will solve the problem. No, it will not. Making the programs robust (where reasonable) is necessary. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message