Arie, I actually disabled this inadvertently when I first moved over to Scalr. The reason is because I moved my databases (including the mysql database) from a CentOS server where there is no user debain-sys- maint. As a result, this user is not allowed to login to the server. I have been running like this for months now with no problems. I suppose you could also just move the /etc/mysql/debian-start script to /etc/ mysql/debian-dont-start or something to diable it running. Mike
On Jan 28, 1:37 pm, Arie Fishler <[email protected]> wrote: > so what's the best way to disable it? the kill statement only removes it > when it is working....but what's the best way not to let it start from the > beginning? > > On Wed, Jan 28, 2009 at 9:27 PM, Frédéric Sidler > <[email protected]>wrote: > > > FYI > > > By default MySQL sue MyISAM, but if you choose to use InnoDB, you might be > > interested by this blog post. The customer Xarb is talking about runs on > > Amazon EC2 > > >http://www.mysqlperformanceblog.com/2009/01/28/the-perils-of-innodb-w... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/scalr-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
