Macports tasks not launching at boot. policy?

["René J.V. Bertin"]

Of course all permissions/ownerships are correct on both the Launch* directories and the plist, and the directories are on a volume that's mounted when the system tries to launch tasks at boot (which in my experience requires that they reside on the boot volume)?


R.


On May 05, 2014, at 06:28, Ryan Schmidt wrote:

> 
> On May 4, 2014, at 18:46, Julien T wrote:
> 
>> 2014-04-24 18:41 GMT-04:00 Ryan Schmidt:
>> 
>>> 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?
>> 
>> 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…
> 
> I’m actually noticing this myself too, on Mavericks; it happens to be with postgresql93-server.