http://qa.mandrakesoft.com/show_bug.cgi?id=1989
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |UNCONFIRMED
Resolution|INVALID |
------- Additional Comments From [EMAIL PROTECTED] 2003-03-05 14:34 -------
Sorry pixel, but I'M not sure what you are trying to say?
Just install RC2 check mysql in drakxservices to be started at boottime and you
will see, that it has no effect, the link is not created right therefore mysql
will not start until you use chkconfig to setup the links correct, chkconfig
will create the link in /etc/rc.d/rc5.d/S90mysql for example, while
drakxservices does always leave the link as K90mysql therfore it will not be
started by the initscript.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
------- Reminder: -------
assigned_to: [EMAIL PROTECTED]
status: UNCONFIRMED
creation_date:
description:
Mysql does not start at bootime in runlevel 3 or 5 due to an bug in drakxservices.
Drakxservices sets up a link(K..mysql) in the appropriate runlevels when marked
to be started at boottime, but it is supposed to setup a link (S..mysql) which
is the correct one to have a service started(S means start K means stop) If you
uncheck mysql in drakxservices, then it completely removes the link instead of
setting up the link as K..mysql.
This error has already been in LM 9.0 and still exists in 9.1 RC1 and cooker
version. I guess the error results from the fact, that chkconfig --list returns
mysql as the last element and the perlscript that uses this list for
drakxservices must handle the last entry(mysql) somehow wrong.
The script is pretty long and I'm not familiar with it, so I don't think I would
be able to findout the error within a reasonable time.
Please check this.
Linux-phased, MandrakeSoft Supportteam
