Quote:
Originally Posted by paul55391
I tried starting a test library on my main drive and launchd didn't start the caliber server, so the problem is probably not with the mounting of the external drive. Manually starting the calibre server with the test library works.
I'm assuming that launchd looks at all the plist files in /Library/LaunchDaemons, and that I need do nothing more that put a plist file in that directory in order for it to be processed by launchd on system startup.
So... I'm still having a problem with this.
|
I know nothing about OSX, so I can't help you any further, but I did find this on Google:
https://developer.apple.com/library/...72i-SW7-108425
Quote:
The launchd Startup Process
After the system is booted and the kernel is running, launchd is run to finish the system initialization. As part of that initialization, it goes through the following steps:
- It loads the parameters for each launch-on-demand system-level daemon from the property list files found in /System/Library/LaunchDaemons/ and /Library/LaunchDaemons/.
- It registers the sockets and file descriptors requested by those daemons.
- It launches any daemons that requested to be running all the time.
- As requests for a particular service arrive, it launches the corresponding daemon and passes the request to it.
- When the system shuts down, it sends a SIGTERM signal to all of the daemons that it started.
|
So your assumption appears to be correct.