Re: [Devil-Linux-discuss] 1.3.4 starting mysql

[Bruce S. <bw...@ar...>]

> > Does the problem occur only when it has to initialize the database?
> > Or only after the database has been initialized?  Or both?
> 
> Both.

This problem may be related.  I'm testing this in VMware server 3i.

I noticed that BIND (named) is also starting weird.  This is a secondary
name server, and only one zone (of many) is being xfered/loaded on boot.
If I restart named after boot, then it loads all zones fine.

I first stuck a 'sleep 30' in the /etc/init.d/named before the start,
and that didn't help at all.

Then I noticed that vmware was starting after named, so I moved vmware
to start before named and syslog, and named seems to start fine on boot.
(with above 'sleep 30' removed)

My new start order:

rc3.d/S05network
rc3.d/S06firewall
rc3.d/S08nut
rc3.d/S08shorewall
rc3.d/S08vmware
rc3.d/S09syslog
rc3.d/S11adsl
rc3.d/S11blankscreen
rc3.d/S11cron
rc3.d/S11dnsmasq
rc3.d/S11domino
rc3.d/S11hotplug
rc3.d/S11mdadm_monitor
rc3.d/S11named
...

Is starting vmware before syslog correct?  Anything else out of order?
Shall I commit these changes?

 - BS