If you ever get into a situation where the gentoo scripts say that
something is running and it is not, you can zap it:
/etc/init.d/mysql zap
That will force it to be in the stopped state. That will enable you to
debug the problem with mysql and be able to start it stop it (or zap it if
it died).
--Jason
On Wed, 6 Aug 2003, 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.
>
> so... any ideas?
>
> --
> [EMAIL PROTECTED] mailing list
>
>
--
Jason A. Pfeil 811 Harbor Winds Dr.
Jacksonville, FL 32225
jason=at=jasonpfeil.com.NOSPAM
--
[EMAIL PROTECTED] mailing list
