Date: Tue, 14 Jun 2005 11:58:36 -0400 From: "Michael W. Lucas" <mwlucas@blackhelicopters.org> To: Vivek Khera <vivek@khera.org> Cc: stable@freebsd.org Subject: Re: /usr/local/etc/rc.d/*.sh not working? Message-ID: <20050614155836.GA63382@bewilderbeast.blackhelicopters.org> In-Reply-To: <590EEFC5-8D42-40F3-B723-F62F478D09D0@khera.org> References: <20050614150240.GA62949@bewilderbeast.blackhelicopters.org> <42AEF361.2010405@t-hosting.hu> <590EEFC5-8D42-40F3-B723-F62F478D09D0@khera.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jun 14, 2005 at 11:22:07AM -0400, Vivek Khera wrote: > > On Jun 14, 2005, at 11:10 AM, K?vesd?n G?bor wrote: > > >For scripts in /usr/local/etc/rc.d You should add an entry to /etc/ > >rc.conf. > >For example, if You script is somedaemon.sh, then add > >somedaemon_enable='YES' to /etc/rc.conf and it will run at the next > >boot. > > > > but his scripts don't use rc-ng, so this is pointless. > > they should just work if they end in .sh and are executable. And this is the million-dollar question: should they? Two things could be causing this behavior: a) old-style .sh scripts are not supported, Michael needs to rewrite them for rcNG b) old-style .sh scripts are supported, Michael has some other system problem If a), fine. If b), though, I need to really start digging. Anyone here know the definitive answer? Thanks for all the help and suggestions, ==ml -- Michael W. Lucas mwlucas@FreeBSD.org, mwlucas@BlackHelicopters.org http://www.BlackHelicopters.org/~mwlucas/ "The cloak of anonymity protects me from the nuisance of caring." -Non Sequitur
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050614155836.GA63382>