[solved] Re: mysqld startup issue

[Gary Aitken]

Ugh.  Operator error.

I assumed from the docs there had to be a my.cnf file someplace,
if only to serve as the system default;
and that the my.cnf file was directing everything else.
It turns out there doesn't have to be one anywhere.
My thought process was hijacked by the errors produced 
from the missing --datadir option

starting using:

  mysqld --datadir=<path> 

was all that was required,
although clearly a my.cnf or ~/.my.cnf would make things easier.

> 120611 10:55:52 [Warning] Can't create test file /var/db/mysql/breakaway.lower-test
> mysqld: Table 'mysql.plugin' doesn't exist
> 120611 10:55:52 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it.
> 120611 10:55:52 InnoDB: The InnoDB memory heap is disabled
> 120611 10:55:52 InnoDB: Mutexes and rw_locks use GCC atomic builtins
> 120611 10:55:52 InnoDB: Compressed tables use zlib 1.2.5
> 120611 10:55:52 InnoDB: Initializing buffer pool, size = 128.0M
> 120611 10:55:52 InnoDB: Completed initialization of buffer pool
> 120611 10:55:52  InnoDB: Operating system error number 13 in a file operation.
> InnoDB: The error means mysqld does not have the access rights to
> InnoDB: the directory.
> InnoDB: File name ./ibdata1
> InnoDB: File operation call: 'create'.
> InnoDB: Cannot continue operation.