Gisella, >Heikki, >I looked at the mysql error log and all the stuff was there. >I was expecting it on the standard output as the documentation said.
it should come to the standard output. I am sending a copy of this email to Miguel of MySQL AB. He should check why mysqld started as --standalone redirects stdout to mysql.err. When mysqld is run as a service it should go to mysql.err, but not when run as standalone. By the way, are you sure you did not have two mysqlds running in your computer? What does the processlist in the Task Manager say? >Thanks again. I'll have to restart the server again since the >innodb monitor output on the error log says that I'm not running a debugable >version, so there is no information about locking. So, I should issue It actually means 'no information about semaphore locking'. You will get the user lock info with innodb_lock_monitor not with plain innodb_monitor. > mysqld-max-nt --debug --standalone >Nothing was printed on stdout when I issued > mysqld-max-nt --standalone >Gisella Regards, Heikki --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
