zap reset it, but it's still not really starting. if i run '/etc/init.d/mysql start', there is no mysql process started. there aren't even any new entries in any log files that i can see from trying to start it.
is anyone else having a similar problem? On Wed, Aug 06, 2003 at 11:24:18PM -0400, gabriel wrote: > On August 6, 2003 11:20 pm, downtime null wrote: > > when i recently ran 'emerge -U world', mysql was upgraded to 4.0 which > > i'm happy about. the only problem is that it won't start and it won't > > stop. when i run '/etc/init.d/mysql start' it says that it's already > > running, but when i run '/etc/init.d/mysql stop' it says '[!!]'. and > > there is never any mysqld running at any time during that process. i > > don't know what happened. i don't know if it ever worked since i > > upgraded. i would suspect that it didn't. > > try: > > # /etc/init.d/mysql zap > # /etc/init.d/mysql start > > "zap" should reset the daemon to appear stopped. > > > -- > we live as though the world is as it should be > to show it what it can be > - angel, angel "deep down" > > > -- > [EMAIL PROTECTED] mailing list > -- [EMAIL PROTECTED] mailing list
