|
|
Nice one (thanks:)
well....I'm not to sure about the .plist "requires" issue. But I do know it works fine on three different OS X boxes which I work on.
For the correct path to mysql.server start, you can perform a: % locate mysql.server presuming you have once already ran: % ./usr/libexec/locate.updatedb (as root) Important! do NOT use safe_mysqld in the SQL startup shell script. This will cause your OS X box to hang at boot time. I had to boot in single user mode to disable the startup script before I could boot my OS X box again. So it's very very important that you call the mysql.server script and not the safe_mysqld script. Cheers Gwyrrdin
Nice one (welcome:)
I noticed that safe_mysqld caused a hang, too.
I *suspect* (though I haven't tried it), that following it with an ampersand (e.g. safe_mysqld &) would make things happier.
You can also make things safer by not running the mysqld as root. One way to do it is:
sudo -u mysql /usr/local/share/mysql/mysql.server start...but it seems like a nasty way to do it. There is reference in the docs to changing the user by using /etc/my.cnf, but my initial experiments haven't yielded anything there.
safe_mysqld &
Actually, you SHOULD use safe_mysqld, because it runs in the background, and will restart mysqld if it stops for any reason. Others have noted correctly that an & after a shell command will make it run in the background. This is how my script looks:
safe_mysqld &
Hello
safe_mysqld &
i stand corrected! |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.05 seconds |
|