From owner-freebsd-questions@FreeBSD.ORG Mon Mar 20 15:09:14 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C74B716A422 for ; Mon, 20 Mar 2006 15:09:14 +0000 (UTC) (envelope-from micahjon@ywave.com) Received: from relay0.av-mx.com (relay0.av-mx.com [137.118.16.125]) by mx1.FreeBSD.org (Postfix) with ESMTP id 52F6043D46 for ; Mon, 20 Mar 2006 15:09:14 +0000 (GMT) (envelope-from micahjon@ywave.com) X-Virus-Scan-Time: 0 Received: from [137.118.16.61] (HELO mx0.av-mx.com) by relay0.av-mx.com (CommuniGate Pro SMTP 4.2.10) with SMTP id 207121605 for freebsd-questions@freebsd.org; Mon, 20 Mar 2006 10:09:13 -0500 Received: (qmail 18980 invoked from network); 20 Mar 2006 15:09:12 -0000 Received: from dsl-12-178-98-182.ywave.com (HELO ?192.168.1.65?) (micahjon@ywave.com@12.178.98.182) by 0 with SMTP; 20 Mar 2006 15:09:12 -0000 X-CLIENT-IP: 12.178.98.182 X-CLIENT-HOST: dsl-12-178-98-182.ywave.com Message-ID: <441EC596.5040308@ywave.com> Date: Mon, 20 Mar 2006 07:09:10 -0800 From: Micah User-Agent: Thunderbird 1.5 (X11/20060113) MIME-Version: 1.0 To: Jerry McAllister References: <200603201438.k2KEcXM4021508@clunix.cl.msu.edu> In-Reply-To: <200603201438.k2KEcXM4021508@clunix.cl.msu.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Bill Schoolcraft , freebsd-questions@freebsd.org Subject: Re: hosts.allow ? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Mar 2006 15:09:14 -0000 Jerry McAllister wrote: >> At Sun, 19 Mar 2006 it looks like Jerry McAllister composed: >> >>> One doesn't start anything from the rc.conf file - at least properly. >>> Those things get started from /usr/local/etc/rc.d. >>> >>> What goes in /etc/rc.conf are environmental variable settings that >>> those rc.d scripts look at to determine what to do. >>> >> I was under the impression that when one 'restarts' that the >> service will "re-read" /etc/rc.conf > > I am not sure just at what point the rc.conf is read or re-read. > Try putting something in the /usr/local/etc/rc.d/xxxx.sh script to > check for a specific environmental variable that you make up and put > in /etc/rc.conf and then running the xxxx.sh script manually to see > what it knows about - even just put a printenv in the script. > > ////jerry From the source it's clear that rc.conf is read when the individual rc script executes a load_rc_config $name (or equivalent). HTH, Micah