2013/6/6 Reindl Harald
>
> Am 06.06.2013 15:39, schrieb Manuel Arostegui:
> > Once that problem has been found...you can use either /etc/init.d/mysql
> > stop or mysqladmin. Both should work in the same way
>
> > You should never use kill
>
> and why? what do you think does any stop command?
>
I
Am 06.06.2013 16:01, schrieb h...@tbbs.net:
> 2013/06/06 09:28 -0400, Mike Franon
> Long story short, 50% of the time the command /etc/init.d/mysqld stop will
> fail
>
> Don't see why it anywhen succeeds. My version of "mysqld" doesn't know "stop"
/etc/init.d/mysqld has *noth
2013/06/06 09:28 -0400, Mike Franon
Long story short, 50% of the time the command /etc/init.d/mysqld stop will
fail
Don't see why it anywhen succeeds. My version of "mysqld" doesn't know "stop".
As for "mysqladmin", it knows "stop", but, since that means "stop-slave", I
doubt
Am 06.06.2013 15:39, schrieb Manuel Arostegui:
> Once that problem has been found...you can use either /etc/init.d/mysql
> stop or mysqladmin. Both should work in the same way
> You should never use kill
and why? what do you think does any stop command?
hint: it sends a SIGTERM
what do you thin
2013/6/6 Mike Franon
> I am running mysql 5.0 for now, and I have a script that I wrote at 12 am,
> that stops mysql server, unmounts the disk that has mysql, and takes a
> different snapshot from amazon as the new disk.
>
>
> Long story short, 50% of the time the command /etc/init.d/mysqld stop
