Date: Sat, 19 Jan 2002 23:08:23 -0800 From: Jim Mock <mij@soupnazi.org> To: Dan Trainor <dan@ript.org> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: question about rc.conf Message-ID: <20020120070823.GD11166@helios.dub.net> In-Reply-To: <00a101c1a180$3b65aed0$0100a8c0@broken> References: <00a101c1a180$3b65aed0$0100a8c0@broken>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 19 Jan 2002 at 23:59:48 -0700, Dan Trainor wrote: > Well, upon further review of the handbook, I came across this - > > Note: Do not place any commands in /etc/rc.conf. To start daemons, or > run any commands at boot time, place a script in /usr/local/etc/rc.d > instead. > > This still leaves me wondering where I would define options found in > the default rc.conf. Should I just hack away at rc.conf, or is there > a program which must invoke such changes? I'm not quite sure what you're talking about exactly. You put foo_bar="YES" (or no) in /etc/rc.conf. Everything in /etc/rc.conf is an override from what's in /etc/defaults/rc.conf. If you're talking about starting up other things like apache and whatnot, a script in /usr/local/etc/rc.d is the way to do it (and the apache port will do that for you). What specifically are you talking about? Give me an example of what you're trying to accomplish. > Also, when cvsup'ing and upgrading a FreeBSD-4.3 box to > FreeBSD-4.5-RC2 box, the ports installation of ssh2 breaks when it > tries to replace the original system-installed (FreeBSD-4.3) version > of sshd. Upon the next reboot, the old sshd server starts, not the > new one. Perhaps some developers are looking at this list, as well. OpenSSH (which is in the base system) can do SSH2. Why not just use that? - jim -- jim mock <mij@soupnazi.org> http://soupnazi.org/ | jim@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020120070823.GD11166>