<div dir="ltr"><div>Sorry for the late answer, yes. That's exactly it.<br><br></div>The 'launchctl load' works for current session but not after reboot.<br>I didn't spot any special message in my system.log, so what could have been mess up...<br>
<div><div><div><div class="gmail_extra"><br><br><div class="gmail_quote">2014-04-24 18:41 GMT-04:00 Ryan Schmidt <span dir="ltr"><<a href="mailto:ryandesign@macports.org" target="_blank">ryandesign@macports.org</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
It has always been the case previously that “sudo port load foo” (which is equivalent to “sudo launchctl load -w /Library/LaunchDaemons/org.macports.foo.plist”) would start the server immediately and at every subsequent system startup, while “sudo port unload foo” (which is equivalent to “sudo launchctl unload -w /Library/LaunchDaemons/org.macports.foo.plist”) would stop the server immediately and prevent it from starting at subsequent system startups.<br>
<br>
Is that no longer happening for you?<br>
<br>
</blockquote></div><br>Julien<br></div></div></div></div></div>