Date: Wed, 15 Nov 2000 05:01:28 +0100 From: dirk.meyer@dinoex.sub.org (Dirk Meyer) To: freebsd-ports@FreeBSD.ORG Subject: Re: ports/22698: Ports' rc.d files should use rc.conf Message-ID: <aMXr25Lv7K@dmeyer.dinoex.sub.org> References: <200011081952.OAA96333@khavrinen.lcs.mit.edu> <wWsGrEkB8l@dmeyer.dinoex.sub.org> <3dgujcf8.fsf@gits.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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. Dirk Meyer wrote: > > 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. Cyrille Lefevre wrote: > another approach is to "chmod -x" every scripts you won't start. Thats looks nice, but you have to remember to do this again, each time you upgrade any port. In my case the port creates a new script in $PREFIX/ect/rc.d and I can keeep a old or modified version of in in rc.local This I have to update by hand. But no port would be started by default. This is fine if you have more than one computer. On the other hand it makes it if the average User much more complicated. My hack works fine for me here. kind regards Dirk - Dirk Meyer, Im Grund 4, 34317 Habichtswald, Germany 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?aMXr25Lv7K>