----------------------------------------------------------------------- WORKLOG TASK -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- TASK...........: Add missing SHUTDOWN statement CREATION DATE..: Thu, 28 Jul 2011, 03:26 SUPERVISOR.....: IMPLEMENTOR....: COPIES TO......: Monty CATEGORY.......: Server-RawIdeaBin TASK ID........: 232 (http://askmonty.org/worklog/?tid=232) VERSION........: WorkLog-4.0 STATUS.........: Un-Assigned PRIORITY.......: 60 WORKED HOURS...: 0 ESTIMATE.......: 0 (hours remain) ORIG. ESTIMATE.: 0 PROGRESS NOTES: DESCRIPTION:

From http://www.jebriggs.com/blog/2011/07/mysqls-missing-shutdown-statement/

Databases are more easily managed if all operations and logging are available to DBAs and scripts at the SQL client command line. So an additional improvement would be to add a SQL command like Oracle’s SHUTDOWN. See the blog post for a comparison table Reference from Oracle: http://www.dba-oracle.com/concepts/shutdown_commands.htm http://dev.mysql.com/doc/refman/5.5/en/mysql-shutdown.html http://dev.mysql.com/doc/refman/5.5/en/server-shutdown.html http://dev.mysql.com/doc/refman/5.5/en/kill.html http://dev.mysql.com/doc/refman/5.5/en/stop-slave.html USD$100 committed from James Briggs at the MariaDB BoF at OSCON 2011 ESTIMATED WORK TIME ESTIMATED COMPLETION DATE ----------------------------------------------------------------------- WorkLog (v4.0.0)