Just to make a confirmation on this old thread.
I reinstalled my Mac with only one partition at daemon are starting right
away.
As the matter is mostly Apple, I think what's important is mostly issue a
warning if at a moment (port update/selfupdate/sync/upgrade) we detect than
/opt is not on /
On May 5, 2014, at 19:08, Eric Gallager wrote:
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
I don’t
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
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
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
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
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,
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
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
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,
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 ryandes...@macports.org:
It has always been
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
Hello,
macports is never setting 'keyRunAtLoad/key' it seems. any option to do
so?
Any policy about it? for provided plist, put it as a comment, enable it by
default?
Some are daemons, some are agents.
It seems agents are started only for user while I was using them more for
cron-like tasks and
Did the user run `port load …` ?
On Apr 24, 2014, at 10:48, Julien T julien@gmail.com wrote:
macports is never setting 'keyRunAtLoad/key' it seems. any option to do
so?
Any policy about it? for provided plist, put it as a comment, enable it by
default?
Some are daemons, some are
2014-04-24 10:55 GMT-04:00 Jeremy Lavergne jer...@lavergne.gotdns.org:
Did the user run `port load …` ?
normally port load is the same as
launchctl load -w /Library/LaunchDaemons/org.macports.${port}.plist
so yes, it was.
but from what re-reading docs gave me, plist doesn't make daemon start
On Apr 24, 2014, at 10:44, Julien T wrote:
2014-04-24 10:55 GMT-04:00 Jeremy Lavergne:
Did the user run `port load …` ?
normally port load is the same as
launchctl load -w /Library/LaunchDaemons/org.macports.${port}.plist
so yes, it was.
but from what re-reading docs gave me, plist
16 matches
Mail list logo
