News for hackers. Stuff that matters.

A comment on What Happened: Adobe Creative Cloud Update Bug. Parent comment

Re:What Happened: Adobe Creative Cloud Update Bug by fivesigma on Monday February 15, 2016 @04:44PM (#11106266)
On OSX with just Photoshop CC installed, there's around 10 adobe related processes running at any given time, all the while making connections and sending data to both adobe and non-adobe (CDNs) IPs. And that's AFTER you disable all of it's settings including run at startup. There's even an adobe Node.js instance (wtf?) constantly running and using CPU.

I don't take kindly to my system being commandeered, so I cancelled my CC subscription, removed their bloated, slimy POS software and bought Affinity Photo.

[ Parent | on HN ]
Re:What Happened: Adobe Creative Cloud Update Bug by maljx on Monday February 15, 2016 @05:02PM (#11106383)
Go to /Library/LaunchDaemons/ and delete what you don't want to run at launch. (At your own risk of course.)
[ Parent | on HN ]
Re:What Happened: Adobe Creative Cloud Update Bug by x0x0 on Monday February 15, 2016 @05:33PM (#11106556)
Better to run "launchctl list | grep -iv com\.apple" for both yourself and root; there are multiple places that startup items can be placed.
[ Parent | on HN ]
Re:What Happened: Adobe Creative Cloud Update Bug by lobster_johnson on Monday February 15, 2016 @05:49PM (#11106652)
Don't delete. Instead, run "launchctl unload -w <file name>". This will stop the service and disable it from loading on boot.
[ Parent | on HN ]
Re:What Happened: Adobe Creative Cloud Update Bug by fivesigma on Monday February 15, 2016 @05:55PM (#11106681)
Tried that, didn't work. My guess is that Photoshop ran some kind of script that re-enabled it. I went to great lengths trying to gracefully disable all the CC crap before I gave up and rm -rf'd every damn file/directory containing adobe.
[ Parent | on HN ]