Sorry for the late answer, yes. That's exactly it. The 'launchctl load' works for current session but not after reboot. I didn't spot any special message in my system.log, so what could have been mess up...
2014-04-24 18:41 GMT-04:00 Ryan Schmidt <[email protected]>: > > 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. > > Is that no longer happening for you? > > Julien
_______________________________________________ macports-users mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-users
