From owner-freebsd-questions@FreeBSD.ORG Mon Sep 11 12:52:17 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 82C0F16A40F for ; Mon, 11 Sep 2006 12:52:17 +0000 (UTC) (envelope-from list-freebsd-2004@morbius.sent.com) Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3ED7C43D5D for ; Mon, 11 Sep 2006 12:52:10 +0000 (GMT) (envelope-from list-freebsd-2004@morbius.sent.com) Received: from frontend3.internal (frontend3.internal [10.202.2.152]) by frontend1.messagingengine.com (Postfix) with ESMTP id 44256DA56DD for ; Mon, 11 Sep 2006 08:52:09 -0400 (EDT) Received: from heartbeat2.internal ([10.202.2.161]) by frontend3.internal (MEProxy); Mon, 11 Sep 2006 08:52:10 -0400 X-Sasl-enc: kp195uwg/MgczcuZkxaXpU22/MfXN90F2mnVlb5e5tyn 1157979129 Received: from [192.168.1.2] (bb-87-81-140-128.ukonline.co.uk [87.81.140.128]) by mail.messagingengine.com (Postfix) with ESMTP id 8D7842099 for ; Mon, 11 Sep 2006 08:52:09 -0400 (EDT) From: RW To: freebsd-questions@freebsd.org Date: Mon, 11 Sep 2006 13:51:56 +0100 User-Agent: KMail/1.9.3 References: <20060910181136.57823.qmail@web34410.mail.mud.yahoo.com> In-Reply-To: <20060910181136.57823.qmail@web34410.mail.mud.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200609111351.58195.list-freebsd-2004@morbius.sent.com> Subject: Re: Making startup order static X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Sep 2006 12:52:17 -0000 On Sunday 10 September 2006 19:11, White Hat wrote: > FreeBSD 6.1 > > I need to keep several programs starting in a > particular order. ... > The problem is that every time I update these programs > the rc.d startup file is modified which destroys the > changes I have made. I've got around this problem in the past by essentially making a new startup file, so foo_enable=YES becomes myfoo_enable=YES, foo.sh becomes myfoo.sh etc. This works reasonably well, because not much actually references local startup files, in the startup sequence. For anything complicated I would write a script to automate patching of the startup scripts.