On Jul 2, 2014, at 4:08 PM, Ryan Schmidt <[email protected]> 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. -- Daniel J. Luke +========================================================+ | *---------------- [email protected] ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+ _______________________________________________ macports-users mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-users
