getting a Start MySQL Failed error in the GUI.. when i attempt to start mysqld from the CLI i get the following error:

? /Applications/MAMP/Library/bin/mysqld         
120623 23:12:47 [Warning] Setting lower_case_table_names=2 because file system for /Applications/MAMP/db/mysql/ is case insensitive
120623 23:12:47 [Note] Plugin 'FEDERATED' is disabled.
120623 23:12:47 InnoDB: The InnoDB memory heap is disabled
120623 23:12:47 InnoDB: Mutexes and rw_locks use GCC atomic builtins
120623 23:12:47 InnoDB: Compressed tables use zlib 1.2.3
120623 23:12:47 InnoDB: Initializing buffer pool, size = 128.0M
120623 23:12:47 InnoDB: Completed initialization of buffer pool
120623 23:12:47 InnoDB: highest supported file format is Barracuda.
120623 23:12:47  InnoDB: Waiting for the background threads to start
120623 23:12:48 InnoDB: 1.1.5 started; log sequence number 1595675
120623 23:12:48 [ERROR] /Applications/MAMP/Library/bin/mysqld: unknown option '--skip-locking'
120623 23:12:48 [ERROR] Aborting

120623 23:12:48  InnoDB: Starting shutdown...
120623 23:12:49  InnoDB: Shutdown completed; log sequence number 1595675
120623 23:12:49 [Note] /Applications/MAMP/Library/bin/mysqld: Shutdown complete

i have deleted the mysql.pid file located at /application/mamp/tmp/mysql/mysql.pid and i still get the error above. I can't find where MAMP has set --skip-locking set, my.cnf doesnt have it anywhere.

Activity monitor gives me a mysqld process running by me, and everytime i KILL the process both via Activity Monitor and via kill =9 pid it starts right back up.. Sampling the process points back to the MAMP mysqld.. wtf?!

About to throw MAMP out the window and boot up a VM of CentOS =)