Red Hat init script

[Please cc me on replies]

In the current Red Hat init script included with the MySQL 4.0.12 RPMs,
mysql is set to run with priority 90. This is, AFAIK, worthless, since
mysql doesn't really depend on anything except possibly network, but
other daemons might depend on mysql, as many do nowadays (e.g. MyDNS,
which in turn everything else that uses DNS could depend on, Courier
MTA, Qmail, both if configured to use MySQL, etc. etc.)
I propose to change the starting priority to 50, right after network,
syslog, and random come up, and before pretty much all of the network
daemons come up.


--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=gcdmb-bugs@m.gmane.org

Re: Red Hat init script

Hello,

Ari Pollak wrote:
> [Please cc me on replies]
>
> In the current Red Hat init script included with the MySQL 4.0.12 RPMs,
> mysql is set to run with priority 90. This is, AFAIK, worthless, since
> mysql doesn't really depend on anything except possibly network, but
> other daemons might depend on mysql, as many do nowadays (e.g. MyDNS,
> which in turn everything else that uses DNS could depend on, Courier
> MTA, Qmail, both if configured to use MySQL, etc. etc.)
> I propose to change the starting priority to 50, right after network,
> syslog, and random come up, and before pretty much all of the network
> daemons come up.

I hope you will agree this is not bug at all so bugs@ is not proper list for it.
Better use mysql@ or internals@ list for this type of questions.

I will disagree with you about starting priority. You are talking about default
setting as distributed with release. This must be suitable for general user for
most common usage of MySQL. It is difficult to prove if possible at all that
having other daemons depending on MySQL is common usage.

Don't forget that MySQL depends on name resolution. This can cause lot of
troubles. Let's say you have MySQL set as Slave on replication schema. Upon
starting it it will need to resolve Master address and if resolving depends on Not
Yet Started DNS it will fail.

At the other hand you are talking about startup script setting which can be very
easily changed by root if necesarry.

Best regards

--
For technical support contracts, visit https://order.mysql.com/?ref=msal
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Mr. Alexander Keremidarski
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Full-Time Developer
/_/ /_/\_, /___/\___\_\___/ Sofia, Bulgaria
<___/ www.mysql.com




--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=gcdmb-bugs@m.gmane.org