Comment 11 for bug 958120

All `sudo mysqld` gives is:

    120813 7:28:50 [ERROR] Fatal error: Please read "Security" section of the manual to find out how to run mysqld as root!
    120813 7:28:50 [ERROR] Aborting
    120813 7:28:50 [Note] /usr/sbin/mysqld: Shutdown complete

/var/log/mysql.err and tail /var/log/mysql.log are empty because mysqld fails to start (for my version of this problem).

syslog has:

Aug 13 07:22:29 AlSSD kernel: [ 1898.934344] init: mysql main process (5335) terminated with status 1
Aug 13 07:22:29 AlSSD kernel: [ 1898.934403] init: mysql main process ended, respawning
Aug 13 07:22:30 AlSSD kernel: [ 1899.947461] init: mysql post-start process (5336) terminated with status 1
Aug 13 07:22:30 AlSSD kernel: [ 1899.984589] init: mysql main process (5363) terminated with status 1
Aug 13 07:22:30 AlSSD kernel: [ 1899.984649] init: mysql main process ended, respawning
Aug 13 07:22:31 AlSSD kernel: [ 1900.997748] init: mysql post-start process (5364) terminated with status 1
Aug 13 07:22:31 AlSSD kernel: [ 1901.027165] init: mysql main process (5391) terminated with status 1
Aug 13 07:22:31 AlSSD kernel: [ 1901.027185] init: mysql respawning too fast, stopped

Because my original failure started with a syslog about apparmor deny, I disabled apparmor with `sudo service apparmor teardown`, but that left me with the messages above during the failed starts.

Could be related to the fact that for me / (where mysqld would load from) is mounted on an an SSD, but /var, /home, and /tmp (where presumably mysqld would create database files) are on an HD.