<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Jul 27, 2019, at 11:16, Ryan Schmidt <<a href="mailto:ryandesign@macports.org" class="">ryandesign@macports.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><span style="caret-color: rgb(0, 0, 0); font-family: Courier; font-size: 24px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">`port select` is a convenience that places symlinks in /opt/local/bin. If `port select` doesn't work, you won't be able to call the programs by their convenient shortened names, but you can still call them by their absolute paths wherever the port put them. You can find out where the port put them by using `port contents mysql57`. For example, if you had wanted to run `mysqld_safe`, you would instead run `/opt/local/lib/mysql57/bin/mysqld_safe`.</span></div></blockquote><br class=""></div><div>Thanks for the clarification. Oddly, the symlink seems to have been created in spite of the port select failure:</div><div><br class=""></div><div>lrwxr-xr-x 1 root wheel 38 Jul 25 08:59 mysqld_safe -> /opt/local/lib/mysql57/bin/mysqld_safe</div><div><br class=""></div><div>The reason I’m a bit wary is that in my previous installation of MySQL there was a symlink that pointed to the correct MySQL (5.7). But, the Launch Daemon was trying to start this: /usr/local/mysql/bin/mysqld_safe --user=mysql, which failed every ten seconds and created the massive (150 million line) error file in the directory for MySQL 5.6.</div><div><br class=""></div><div>I’m assuming that the symlink was created when I initially installed MySQL (5.6) but wasn’t updated when it was upgraded to 5.7. </div><div><br class=""></div><div>I’d like for that not to happen again. </div><br class=""></body></html>