Date: Fri, 11 Dec 1998 22:31:23 -0800 (PST) From: dima@best.net (Dima Ruban) To: shmit@kublai.com Cc: dima@best.net, dillon@apollo.backplane.com, jkh@zippy.cdrom.com, des@flood.ping.uio.no, committers@FreeBSD.ORG Subject: Re: /etc/rc.local Message-ID: <199812120631.WAA76971@burka.rdy.com> In-Reply-To: <19981212001742.L29799@kublai.com> from Brian Cully at "Dec 12, 1998 0:17:42 am"
next in thread | previous in thread | raw e-mail | index | archive | help
Brian Cully writes: > > Yes, it wouldn't be hard to do it, but I don't exactly see a point > > doing it. rc.local is empty and usually it stays empty (or almost empty). > > It does? I've rarely worked with a machine that has an empty > rc.local. What if I want to run MySQL, or Apache, or ftpd in stand > alone mode, or any of the millions of other things that people can > do in rc.local? > > I'd say that the common case is that rc.local has custom stuff in > it. > > In any event, I know I'm not the only sysadmin that looks for > stuff in rc.local. I've meant that rc.local from the distribution is practially empty. There's no point updating it with sysinstall. All it does - it reads rc.conf variables (if you allow it) and either based on that (or not) executes some stuff. I find it kinda convenient in it's _current_ mode. > > -bjc > -- dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199812120631.WAA76971>