I created the my.cnf file (for some reason, it was nowhere to be found) and
passed it as an argument to mysqld_safe . That's it! Works beautifully
now.
Thanks,
Sachin
On 4/3/06, Greg 'groggy' Lehey <[EMAIL PROTECTED]> wrote:
>
> On Monday, 3 April 2006 at 2:29:48 +0530, Sachin Petkar wrote
On Monday, 3 April 2006 at 2:29:48 +0530, Sachin Petkar wrote:
> On 4/3/06, Eric Braswell <[EMAIL PROTECTED]> wrote:
>>
>> Sachin Petkar wrote:
>>> For some reason, MySQL 4.0.18 has suddenly stopped running and will not
>>> start anymore.
>>>
>>> ...
>>
>> There are several possible reasons for t
Thanks to everyone, MySQL is back up and running.
This was definitely enlightening!
Sachin
On 4/3/06, Eric Braswell <[EMAIL PROTECTED]> wrote:
>
> Sachin Petkar wrote:
> > For some reason, MySQL 4.0.18 has suddenly stopped running and will not
> > start anymore.
> >
> > It has been running for s
Sachin Petkar wrote:
For some reason, MySQL 4.0.18 has suddenly stopped running and will not
start anymore.
It has been running for several weeks until about 5 days ago. When I tried
to reach it, I discovered that it is no longer running. However,
attempting to start it via the mysqld_safe sc
Here are some screen snapshots of qps showing mysql server
running on my machine.
I tries to post these to the list, but they went over the
file size limit for the mailing list.
Showing mysql running in memory without using mysqld_safe script:
http://www.karsites.net/KAR/websites/pub/computing
Do you have some sort of visual process manager for Mac OS X
that can tell you at a glance if mysqld_safe and mysql
server are actually running in memory?
Under linux I use a program called qps.
http://www.student.nada.kth.se/~f91-men/qps/
You may already have a similar utility to view running
