I wonder if you have a badly defined service that's just making it lose its mind.
I would start by trolling through ~/Library/LaunchAgents/, ~/Library/LaunchDaemons/, /Library/LaunchAgents/, and /Library/LaunchDaemons/ and try to determine if anything looks out of place.
FWIW, `launchctl` is the CLI program you use to interact with `launchd`. If you're familiar with RHEL/CentOS and `systemctl`, you'll find it to have similarities because IIRC `launchd`/`launchctl` actually inspired the creation and definition of `systemd`/`systemctl` (but `systemd` continued to grow like a weed, much to some sysadmins' dismay…).
`launchctl help` will give you an overview of its subcommands, but `man launchctl` will probably be required reading to really understand the various arguments. `launchctl list` will list all known services, and that's another strategy to identify any possible rogue items. If you think a particular service is misbehaving, try to `launchctl print`, `launchctl blame`, `launchctl stop`, `launchctl unload`, and `launchctl remove` it (in that order).
|