Date: 15 Nov 2000 01:39:55 +0100 From: Cyrille Lefevre <clefevre@cybercable.fr> To: dirk.meyer@dinoex.sub.org (Dirk Meyer) Cc: freebsd-ports@FreeBSD.ORG Subject: Re: ports/22698: Ports' rc.d files should use rc.conf Message-ID: <3dgujcf8.fsf@gits.dyndns.org> In-Reply-To: dirk.meyer@dinoex.sub.org's message of "Thu, 09 Nov 2000 05:12:56 %2B0100" References: <200011081952.OAA96333@khavrinen.lcs.mit.edu> <wWsGrEkB8l@dmeyer.dinoex.sub.org>
next in thread | previous in thread | raw e-mail | index | archive | help
dirk.meyer@dinoex.sub.org (Dirk Meyer) writes: > Garrett Wollman wrote: > > > We have several machines which are set up with identical software, for > > cold-sparing purposes. Not all of these machines run the same set of > > daemons. IWNRNI the standard rc.d/foo.sh files checked rc.conf to > > find out whether or not they should be enabled. > > I use a far simpler approach. I just set in my rc.conf: > > local_startup="/usr/local/etc/rc.local" > > and set a link or copy of the .sh file in this directory on each machine. another approach is to "chmod -x" every scripts you won't start. Cyrille. -- home: mailto:clefevre@citeweb.net work: mailto:Cyrille.Lefevre@edf.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3dgujcf8.fsf>