Re: Macports tasks not launching at boot. policy?
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. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Macports tasks not launching at boot. policy?
On May 5, 2014, at 05:18, René J.V. Bertin wrote: 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)? In my case, MacPorts is on a separate partition, but it’s the same physical disk as the boot partition. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Macports tasks not launching at boot. policy?
2014-05-05 6:18 GMT-04:00 René J.V. Bertin rjvber...@gmail.com: 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)? That could be the point. I'm pretty sure it was working one or two months ago. But I switch to macports 2.2.99 to move /opt to another volumes which is still on the boot disk but a second partition with a /opt symlink. If it's really the case, it means launchd is starting before other volumes are mounted, even for the local one ... :( Not sure if there is a way to make it work in this configuration. If it is confirmed, a warning should be issued when doing 'port load' that it is not working at boot if symlink structure exists And, no, RunAtLoad is not fixing it. Permissions are good (755/644) Julien ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Macports tasks not launching at boot. policy?
I search a bit the web to know when non-system partition are mounted but it seems unclear. Many people seems to do a mount script+plist to mount various network partition. As a launchd option, PathState could be a solution to try http://stackoverflow.com/questions/19449288/how-to-instruct-launchd-to-wait-for-volume-mount https://developer.apple.com/library/mac/technotes/tn2083/_index.html or maybe on OtherEnabledJob with automountd but not sure if it handles local volume or only network ones. These page are on boot sequence but nothing about alternate partition/volume http://en.wikipedia.org/wiki/Launchd http://busylog.net/mac-osx-boot-sequence-launchd/ http://www.cnet.com/news/troubleshooting-the-boot-process-for-intel-macs/ It seems to be an old problem (2007 at least) https://www.mail-archive.com/macports-users@lists.macosforge.org/msg03498.html Julien ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Macports tasks not launching at boot. policy?
On Mon, May 5, 2014 at 7:17 AM, Julien T julien@gmail.com wrote: If it's really the case, it means launchd is starting before other volumes are mounted, even for the local one ... :( launchd is the process that starts the system; the only mounted volume is / when it starts. That said, perhaps it should distinguish between minimal stuff needed to get the system running and normal operating... but I'm not sure that would occur to Apple. :/ -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Macports tasks not launching at boot. policy?
On May 05, 2014, at 14:52, Brandon Allbery wrote: On Mon, May 5, 2014 at 7:17 AM, Julien T julien@gmail.com wrote: If it's really the case, it means launchd is starting before other volumes are mounted, even for the local one ... :( launchd is the process that starts the system; the only mounted volume is / when it starts. That said, perhaps it should distinguish between minimal stuff needed to get the system running and normal operating... but I'm not sure that would occur to Apple. :/ Exactly - my system is set to verbose booting, and I can clearly see the complaint about all of MacPorts' Launch* plists not existing (they're symlinked from /Library/Launch* to /opt/local/Library/Launch*, with /opt/local itself being a symlink to a 2nd partition on my boot disk). Maybe it'd be possible to trigger the mounting of local partitions through launchd ... assuming one can control the order in which launchd scripts are executed? R. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Macports tasks not launching at boot. policy?
On Mon, May 5, 2014 at 9:03 AM, René J.V. Bertin rjvber...@gmail.comwrote: Maybe it'd be possible to trigger the mounting of local partitions through launchd ... assuming one can control the order in which launchd scripts are executed? Well, there's this bit where launchd does stuff via the plists, so this only works if you can arrange for it to load one set, execute stuff from it, then load the rest. If it loads them all in one pass, then you have the problem that you need to force stuff to be mounted before launchd does the scan --- but launchd determines what to do by scanning and loading plists, and *nothing else* is running before launchd starts. In short, given that it's not working as is, you're looking at modifying launchd itself. (Remember, launchd is init.) There is not likely to be any kind of clever workaround. -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: macports or meld issue?
On Mon, 2014-05-05 at 11:54 -0400, Gus Heck wrote: I'm having more or less exactly this issue: https://www.mail-archive.com/meld-list@gnome.org/msg02071.html on OSX 10.9.2... I had never found need to use any of homebrew/fink/macports but apparently fink or macports is the recommended way to get meld and I wanted to get meld... after many many minutes of downloading dependencies (my connection is 25/25 Business class fiber, so clearly the source locations must be slow or meld is bigger than TexShop... ) all I got for my effort was http://pastebin.com/3QptJPsz. FWIW, I run meld on Mac OS X 10.9 all the time. You have to start dbus like Jeremy said, but that's all I had to do to get meld working through MacPorts. All the best, Jason -- Jason M. Swails BioMaPS, Rutgers University Postdoctoral Researcher ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Macports tasks not launching at boot. policy?
If you want to try modifying the launchd sources, you might want to have a look at the openlaunchd fork of it, as it seems to be more up-to-date than the version on opensource.apple.com at least: https://github.com/rtyler/openlaunchd On 5/5/14, Brandon Allbery allber...@gmail.com wrote: On Mon, May 5, 2014 at 9:03 AM, René J.V. Bertin rjvber...@gmail.comwrote: Maybe it'd be possible to trigger the mounting of local partitions through launchd ... assuming one can control the order in which launchd scripts are executed? Well, there's this bit where launchd does stuff via the plists, so this only works if you can arrange for it to load one set, execute stuff from it, then load the rest. If it loads them all in one pass, then you have the problem that you need to force stuff to be mounted before launchd does the scan --- but launchd determines what to do by scanning and loading plists, and *nothing else* is running before launchd starts. In short, given that it's not working as is, you're looking at modifying launchd itself. (Remember, launchd is init.) There is not likely to be any kind of clever workaround. -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
