Date: Tue, 14 Jun 2005 17:10:25 +0200 From: =?ISO-8859-1?Q?K=F6vesd=E1n_G=E1bor?= <gabor.kovesdan@t-hosting.hu> To: "Michael W. Lucas" <mwlucas@blackhelicopters.org> Cc: stable@freebsd.org Subject: Re: /usr/local/etc/rc.d/*.sh not working? Message-ID: <42AEF361.2010405@t-hosting.hu> In-Reply-To: <20050614150240.GA62949@bewilderbeast.blackhelicopters.org> References: <20050614150240.GA62949@bewilderbeast.blackhelicopters.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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. Cheers, Gábor Kövesdán Michael W. Lucas wrote: >I'm certain this is documented somewhere, but danged if I can find it. > >I have a whole variety of custom scripts in /usr/local/etc/rc.d. For >years now, simply giving them a name ending in .sh and making them >executable has been sufficient to make them start on boot. > >On 5.x, it's not. And now, having upgraded to 4.11-s on some older >boxes and running portupgrade -a, it's not. > >Obviously these scripts need something else. There's no fancy rcNG >infrastructure in them; is rcNG a requirement for startup scripts now? >Any pointers on where I can find the right documentation? > >Thanks, > >==ml > > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42AEF361.2010405>