Am Samstag, 19. Oktober 2002 21:51 schrieb David Guntner: > This question was asked by someone else earlier, but I never saw a > response. Sorry if one was given and I was just being blind... :-) > > I've done "chkconfig --add mysql" so I know it should be starting. When > checking the comments at the beginning of the /etc/rc.d/init.d/mysql > script, I see: > > # Comments to support chkconfig on RedHat Linux > # chkconfig: 2345 90 90 > # description: A very fast and reliable SQL database engine. > > Which says that it should be getting started in run levels 2 through 5. > And yet, upoon booting, there's no mysql daemon running. I have to > manually do a "/etc/init.d/mysql start" to bring it up. Checking the > startup configuration, I find: > > # chkconfig --list mysql > mysql 0:off 1:off 2:on 3:off 4:on 5:off 6:off > > Ok, so how come mysql is only set to come in in run levels 2 and 4, when > the comments at the beginning of the script say 2 through 5? > > I'm thinking that maybe it's related to running msec level 4. If that's > the case, how do you override and tell it to allow that service to run > at startup? > > Any help would be appreciated. > > --Dave
Hey, a little late, but I found the sollution. The 'off' in runlevel 3 and 5 is caused by the lsb stuff. somewhere in the mysql file in /etc/init.d there are the lines # Default-Start: 3 5 # Default-Stop: 3 5 but they should be # Default-Start: 2 3 4 5 # Default-Stop: 1 6 I is obvious, now, why runlevel 3 and 5 does not start mysql. Its a Bug in the mysql init-script. Martin -- ------------------------------------------------------------ H E L I X Gesellschaft für Software & Engineering mbH ------------------------------------------------------------ Hanauer Landstrasse 52 Telefon (069) 4789 35-30 60314 Frankfurt am Main Telefax (069) 4789 35-44 ------------------------------------------------------------ http://www.helix-gmbh.net [EMAIL PROTECTED] ------------------------------------------------------------
msg63025/pgp00000.pgp
Description: signature
