Date: Wed, 2 Feb 2000 17:48:21 -0500 (EST) From: John Woodruff <jjw@us.net> To: freebsd-isp@freebsd.org Subject: Re: controlling local boot sequence Message-ID: <200002022248.RAA49648@laurel.us.net> In-Reply-To: <20000201175018.A21189@infoteam.com> from Kenn Martin at "Feb 1, 2000 05:50:18 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
This may seem like a far-out suggestion, but has anyone considered replacing the whole idea of a sequence of startup scripts with a concatenation of makefiles? Consider something like this: in file /etc/rc.network.m: START: network network: ifconfig ... in file /etc/rc.named.m: START: named named: network named ... in file /usr/local/etc/rc.apache.m: START: apache apache: named network apachectl ... Then, in /etc/rc or somewhere thereabouts: cat /etc/rc.*.m /usr/local/etc/rc.*.m | make -ik -f - START The idea is that you list everything that you need running when you start, and make figures out the right order. Just like now, no files need editing when you add a new subsystem. If a particular thing fails (say, MySQL), make won't start things that say they need it, but still starts things that don't (see the -k flag). > 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? 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?200002022248.RAA49648>