[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: insserv + apache2 + bind9 = pain



On Tue, 28 Dec 2010 10:06:58 -0800, Mike Bird wrote:

> On Tue December 28 2010 01:31:50 Camaleón wrote:
>> On Tue, 28 Dec 2010 00:10:23 -0800, Mike Bird wrote:
>> > Is it possible to go back to the old system?
>>
>> If you mean "how to disable dependency booting" yes, you can disable it
>> to get the old behaviour, but you will still have to ensure bind9 is
>> started before apache2:
>>
>> http://www.debian.org/releases/squeeze/i386/release-notes/ch-whats-
new.en.h
>>tml#dependency-boot
> 
> Thank you Camaleón.
> 
> CONCURRENCY=none may help some people with different problems, but it
> does not solve the problem of unexpressed dependencies.

Old booting style neither, you also have to "juggle" things to get the 
desired order ;-)

JFYI:

apache2: fails to start with dependency based boot if DNS is required by 
configuration
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606334
 
> Is there a way to use the old-style reliable init system based on the
> Snn and Knn values in rcn.d?  Real servers have dependencies among
> numerous server processes.  A few of these dependencies relate to Debian
> packaging but far more relate to configuration, scripting, plugins, and
> even custom programming.

Old booting style has nothing reliable, so before ditching dependency 
booting at all I would recommend you to first find out what is failing at 
your side and why.

> It is simply not worth the effort to spend hours trying to discover and
> express all the dependencies on a bunch of servers in order to save half
> a second of boot time once per year.  It took me four hours to discover
> what was wrong in a very simple case.  This was not helped by failures
> to log errors, bootchart2 missing from Squeeze, a near complete lack of
> documentation, and insserv silently ignoring errors in my early attempts
> to express missing dependencies.

It is somehow documented (man insserv).

> I've read the very thin /usr/share/doc and man documentation and googled
> extensively.  The new system may be great for script kiddies rebooting
> their Ubuntu laptops twice a day but it is an appalling idea for Debian
> servers.  It not only scales terribly (on the order of N squared
> dependencies instead of N priorities) but is also very poorly
> documented.

I've been using insserv (dependecy based booting) with openSUSE since 
years and this method really works quite well, so no, not intended just 
for kiddies :-)

OTOH, I suppose (although not tested and not sure if disabling at all is 
nowadays even possible :-?) that by reconfiguring "insserv" package you 
could restore the old sysinit booting style... but think it twice before 
going back to the cavern :-P

Greetings,

-- 
Camaleón


Reply to: