[macosx-unix] launchd [was: amanda backup]

[Jan Schaumann]

Jan Schaumann <jschauma at netmeister.org> wrote:
 
> I'm quite sure that the plist itself, as is, is correct.  It does work
> just fine when I manually 'launchctl load' it, after all.  It just
> doesn't start automatically, *even though* it's actually loaded
> automatically.  That is, after a fresh reboot, 'launchctl list' will
> show me that org.amanda.amanda is a service that is running, only it
> will not actually be running and nothing is listening on port 10080.

I believe the problem is that the binary is located on a different
Volume than the root Volume.  So at boot time, whenever launchd actually
starts all the services, the other Volume is not yet mounted.  When I
log in lateron, it is mounted and re-starting the service works.

launchd does not seem to allow you to specify a specific order -- I
believe that that is actually somehow argued to be an advantage of
launchd.

In NetBSD, I can specify which partitions need to be mounted before the
system tries to start anything else, but I take it that under OS X
that's not possible.  Probably one more of those ``Oh, why would anybody
want to do _that_?  Let's make it impossible.'' Apple things.

Prove me wrong.  Please. :-)

-Jan

-- 
``Californians have gotten to the point of being completely intolerant
of non-diversity.'' -- Larry Wall
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 186 bytes
Desc: not available
Url : http://berdom.net/pipermail/macosx-unix/attachments/20060316/01cfabc2/attachment.bin