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
Regards
Keith
In theory, theory and practice are the same;
in practice they are not.
On Sun, 2 Apr 2006, Sachin Petkar wrote:
> To: mysql@lists.mysql.com
> From: Sachin Petkar <[EMAIL PROTECTED]>
> Subject: MySQL 4.0.18 on Mac OS X 10.2.8 won't start
>
> For som
l.com
> From: Sachin Petkar <[EMAIL PROTECTED]>
> Subject: MySQL 4.0.18 on Mac OS X 10.2.8 won't start
>
> 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.
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 script simply returns wit
