On Jul 2, 2014, at 3:15 PM, Daniel J. Luke <dl...@geeklair.net> wrote:
> On Jul 2, 2014, at 4:08 PM, Ryan Schmidt <ryandes...@macports.org> wrote: >>> For some reason my MacPorts installed ports don't stay loaded with `port >>> load foo` on that machine (ie, when I reboot squid3 doesn't start up >>> unless/until I do another `port load squid3`). I haven't had time to >>> investigate why (yet). >>> >>> It wouldn't be (much) of an issue either, but I've been seeing a (widely >>> reported) tcp stack bug on Mavericks which means I end up rebooting that >>> machine way more often than I normally would have to. >> >> Is your MacPorts prefix on a different volume than your OS X startup volume? >> That's apparently a problem now, in that launchd tries to load the plist >> before the volume that the plist is on has been mounted. > > yes, that's most likely the issue. I haven't bothered to copy the files over > (or make my own launchd plists) to verify yet. We discussed this issue on the list some weeks back and there may be a way we could modify the way MacPorts generates the plists to overcome this problem but I haven't had time to try it out yet. _______________________________________________ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
