"Feedback" <[EMAIL PROTECTED]> wrote: > Besides that, the server has also a lot of trouble with the fact that = > sometimes the MySQLd just stops functionizing somehow, and the only way = > to kill the (all child processes broke down, so i mean the parent) = > process is 'killall -9 mysqld'. 'kill <pid>' doesn't work, and = > '/etc/init.d/mysql stop' neither. Sometimes the whole server crashes, no = > SSH/ping, and the only option to get it back only is through the reboot =
That's the point! I don't think it's a MySQL issue. A piece of software cannot hang all the OS (by the exception of a well-known OS ;). -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Egor Egorov / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
