From owner-freebsd-stable@FreeBSD.ORG Tue Jun 14 15:19:41 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B407816A41C for ; Tue, 14 Jun 2005 15:19:41 +0000 (GMT) (envelope-from mwlucas@bewilderbeast.blackhelicopters.org) Received: from bewilderbeast.blackhelicopters.org (bewilderbeast.blackhelicopters.org [198.22.63.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 70D0E43D4C for ; Tue, 14 Jun 2005 15:19:41 +0000 (GMT) (envelope-from mwlucas@bewilderbeast.blackhelicopters.org) Received: from bewilderbeast.blackhelicopters.org (mwlucas@localhost [127.0.0.1]) by bewilderbeast.blackhelicopters.org (8.12.10/8.12.10) with ESMTP id j5EFJdOu063103; Tue, 14 Jun 2005 11:19:39 -0400 (EDT) (envelope-from mwlucas@bewilderbeast.blackhelicopters.org) Received: (from mwlucas@localhost) by bewilderbeast.blackhelicopters.org (8.12.10/8.12.10/Submit) id j5EFJdhp063102; Tue, 14 Jun 2005 11:19:39 -0400 (EDT) (envelope-from mwlucas) Date: Tue, 14 Jun 2005 11:19:39 -0400 From: "Michael W. Lucas" To: K?vesd?n G?bor Message-ID: <20050614151939.GA63065@bewilderbeast.blackhelicopters.org> References: <20050614150240.GA62949@bewilderbeast.blackhelicopters.org> <42AEF361.2010405@t-hosting.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <42AEF361.2010405@t-hosting.hu> User-Agent: Mutt/1.4.1i X-Spam-Score: (0) X-Scanned-By: MIMEDefang 2.39 Cc: stable@freebsd.org Subject: Re: /usr/local/etc/rc.d/*.sh not working? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Jun 2005 15:19:41 -0000 That works fine for ports, but what about truly local custom scripts? For example, I have a server with about 400 separate MRTG daemons on it. (Yes, they must be separate, for administrative rather than technical reasons.) Each daemon has a custom script. These aren't ports, and they have no rcNG infrastructure. They used to work fine. Now they don't. Obviously something has changed. I'd like to have just a plain old /usr/local/etc/rc.d/*.sh file get executed on boot, like it used to be, but if I have to change the scripts I will. On Tue, Jun 14, 2005 at 05:10:25PM +0200, 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. > > 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 > > > > > > -- 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