Lingon X presents all the launchd configuration files in a list to the left so you can easily search and choose which one to edit. WordPress.com Lingon X review: Powerful job scheduler for your Mac
: Power users sometimes prefer LaunchControl , which some feel offers deeper technical capabilities for the same price point. Lingon X – Control Your Hidden Daemons - Mause Reviews
: Includes a feature to automatically relaunch apps if they crash or quit unexpectedly.
: Lists all launchd items, including those specific to your user account, all users, or root.
Lingon X 7.4.3 May 2026
Lingon X presents all the launchd configuration files in a list to the left so you can easily search and choose which one to edit. WordPress.com Lingon X review: Powerful job scheduler for your Mac
: Power users sometimes prefer LaunchControl , which some feel offers deeper technical capabilities for the same price point. Lingon X – Control Your Hidden Daemons - Mause Reviews Lingon X 7.4.3
: Includes a feature to automatically relaunch apps if they crash or quit unexpectedly. Lingon X presents all the launchd configuration files
: Lists all launchd items, including those specific to your user account, all users, or root. Lingon X 7.4.3
This could have to do with the pathing policy as well. The default SATP rule is likely going to be using MRU (most recently used) pathing policy for new devices, which only uses one of the available paths. Ideally they would be using Round Robin, which has an IOPs limit setting. That setting is 1000 by default I believe (would need to double check that), meaning that it sends 1000 IOPs down path 1, then 1000 IOPs down path 2, etc. That’s why the pathing policy could be at play.
To your question, having one path down is causing this logging to occur. Yes, it’s total possible if that path that went down is using MRU or RR with an IOPs limit of 1000, that when it goes down you’ll hit that 16 second HB timeout before nmp switches over to the next path.