Date: Sat, 31 Jul 2004 18:43:57 +0300 From: Mike Makonnen <mtm@identd.net> To: Andrey Chernov <ache@nagual.pp.ru>, Oliver Eikemeier <eikemeier@fillmore-labs.com> Cc: current@FreeBSD.ORG Subject: Re: RFC: Alternate patch to have true new-style rc.d scripts in ports (without touching localpkg) Message-ID: <20040731154357.GA35674@rogue.acs-et.com> In-Reply-To: <20040731153303.GA6471@nagual.pp.ru> References: <20040731104933.GA1312@rogue.acs-et.com> <03C7D82F-E2F5-11D8-9C56-00039312D914@fillmore-labs.com> <20040731145616.GA14576@rogue.acs-et.com> <20040731150542.GA5612@nagual.pp.ru> <20040731151944.GA23710@rogue.acs-et.com> <20040731153303.GA6471@nagual.pp.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jul 31, 2004 at 07:33:03PM +0400, Andrey Chernov wrote: > On Sat, Jul 31, 2004 at 06:19:44PM +0300, Mike Makonnen wrote: > > scripts that have a .sh, and those that don't. If you really want > > your script to be sourced in the same shell, then you give it a > > .sh extension. Otherwise, it will be sourced in a subshell. So, when > > It can make things even worse, what if someone rename his rc.subr-ed > script.sh to script.sh.old ? It was common practice in the past to not > execute anything without .sh at all. I think I already answered this in a previous thread, but here goes again. If it is an old style script (not rc.d) then it gets executed only if it has a .sh extension and it is executable. That has NOT changed. If it is an rc.d script then it gets executed only if the appropriate foo_enable knob is turned on. Cheers. -- Mike Makonnen | GPG-KEY: http://www.identd.net/~mtm/mtm.asc mtm@identd.net | Fingerprint: AC7B 5672 2D11 F4D0 EBF8 5279 5359 2B82 7CD4 1F55 mtm@FreeBSD.Org| FreeBSD - Unleash the Daemon !
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040731154357.GA35674>