From owner-freebsd-isp Tue Feb 1 16:11:40 2000 Delivered-To: freebsd-isp@freebsd.org Received: from seidata.com (mail.seidata.com [208.10.211.10]) by builder.freebsd.org (Postfix) with ESMTP id 5AEA43E71 for ; Tue, 1 Feb 2000 16:11:31 -0800 (PST) Received: from localhost (pboehmer@localhost) by seidata.com (8.9.3/8.9.3) with ESMTP id TAA21146; Tue, 1 Feb 2000 19:12:09 -0500 (EST) Date: Tue, 1 Feb 2000 19:12:09 -0500 (EST) From: Paul Boehmer To: Kenn Martin Cc: freebsd-isp@FreeBSD.ORG Subject: Re: controlling local boot sequence In-Reply-To: <20000201175018.A21189@infoteam.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Kenn, We noticed that the scripts in rc.d are started in alpa-numeric order, so when we run into dependency problems we'll rename scripts like 1_program.sh or A_program.sh 2_program.sh or B_program.sh 3_program.sh or C_program.sh and so on. This was our solution, take it with a grain of salt. Paul Boehmer Systems Administrator SEI Data, Inc. pboehmer@seidata.com On Tue, 1 Feb 2000, Kenn Martin wrote: > Looking for some tips on controlling local startup sequences when > using MySQL. I imagine that other ISPs have similar configurations. > > FreeBSD 3.4-STABLE machines, scripts in /usr/local/etc/rc.d (some > created by /usr/ports/* and some myself). Script names end in .sh, > are executable, and are named starting with numbers so as to > attempt to control sequencing. > > The problem we are experiencing is that at boot time, MySQL is being > loaded but other packages which depend on MySQL, such as Apache and > ICRADIUS, often fail. These packages are probably starting before MySQL > finishes its initialization. I know the /etc/periodic files are named > with a numbering scheme so I tried that in /usr/local/etc/rc.d without > any consistent success. Packages that fail to start during the boot > process can be started manually using these exact same scripts. > > It appears that I can merge the multiple scripts into one master script, > but that doesn't exactly seem like the proper way to handle the problem. > > How do others handle these type of dependencies? > > kenn > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isp" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message