[hellojason]

Care to share?

[luckman212]

Sure. It requires a tiny bit of setup, but I put up a gist[0].

You can customize to your needs/liking, let me know if it works for you...

[0]: https://github.com/luckman212/adobe_kill

[ValentineC]

This is mine from 2019:

  sudo killall ACCFinderSync “Core Sync” AdobeCRDaemon “Adobe Creative” AdobeIPCBroker node “Adobe Desktop Service” “Adobe Crash Reporter”

I should probably stick it in Automator or something because Adobe's invasion is getting really annoying.

[MiguelHudnandez]

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-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.

[saagarjha]

Speaking of launchd, it would be a much better idea to unload those services rather than just killing them so they don't come back.

[MiguelHudnandez]

Indeed. Some component of Adobe's suite will be responsible for re-enabling them, so it's just a balance between actually using the software and disabling the background tasks.