Date: Tue, 1 Feb 2000 21:07:37 -0500 From: Kenn Martin <kmartin@infoteam.com> To: freebsd-isp@FreeBSD.ORG Subject: Re: controlling local boot sequence Message-ID: <20000201210737.B23264@infoteam.com> In-Reply-To: <Pine.BSF.4.10.10002011908570.19303-100000@mailer.seidata.com>; from pboehmer@seidata.com on Tue, Feb 01, 2000 at 07:12:09PM -0500 References: <20000201175018.A21189@infoteam.com> <Pine.BSF.4.10.10002011908570.19303-100000@mailer.seidata.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Feb 01, 2000 at 07:12:09PM -0500, Paul Boehmer wrote: > 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. That is what we have today (see below, "named starting with ..."). It made it somewhat more reliable, but it seems that the number of databases, or some such factor, affects the MySQL startup which might be forked. > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000201210737.B23264>