launchd sounds scary but it is not that hard to get an agent enabled. It's basically a plist file or two in the right place and a command to enable it. You ca

launchd sounds scary but it is not that hard to get an agent enabled. It's basically a plist file or two in the right place and a command to enable it. You can have launchd call your shell script once per minute. I used this to good effect once to log the output of a few debug commands to text, commit that to a git repo, and move on. Then I could come back later and see what was going on before an issue happened on that system. Here's some info on launchd to save you some searching: https://www.maketecheasier.com/use-launchd-run-scripts-on-schedule-macos/ https://www.maketecheasier.com/use-launchd-run-scripts-on-sc... Regarding finding the adobe process names, you can filter output of `ps aux` based on application path or name to get a current list process IDs and kill those. In this particular case, watch out for getting into a launchd fight, where launchd is simultaneously killing adobe processes and also relaunching them because of Adobe's own launchd registrations.