![]() Before we actually move to solve the problem, let us briefly cover how to run processes in the background. To deal with these two issues, you need to totally detach a process from a controlling terminal. in the event that the terminal is closed, the process together with its child processes will be terminated.your controlling terminal is filled with so much output data and error/diagnostic messages.When a process is associated with a terminal, two problems might occur: HELLO ADOBE: I don't want or need you rifling my disk when I'm not there, or running my CPU all the time to support, what?, better-educated guesses at what I might want to buy from you next? As gp7024 says - I'm paying you to do something specific on my computer, and I don't want you doing other unwanted stuff and absorbing my resources doing it.In this guide, we shall bring to light a simple yet important concept in process handling in a Linux system, that is how to completely detach a process from its controlling terminal. And then I'll curse Adobe again for making this all difficult. ![]() Now, someday I'm going to run into a situation where one of these closed processes is actually needed, and if it doesn't reload itself then, I may have a headscratcher issue that will resolve with a reboot. In my case, I grumble loudly and close the offending processes. So I have been angered & annoyed to see my process list in Task Manager include several Adobe CC-related ones that are among the top consumers of CPU and disk I/O. I am like you - I occasionally use PS and LR, but most of the time I'd prefer not to have them running, as I am not an imaging professional. Why is it left up to me the user to keep this folder tidy? It's sloppy design. I am a retired, software engineer and I think I am entitled to expect Adobe to respect my opinion.Īlso there is the issue of why so many files get created in the Temp folder and do not get cleared out. I hope someone from Adobe design sees this. This is my machine not Adobe's I don't want this stuff running on MY computer (unless its doing something useful). They just coded it the easy way, let it run regardless. This is bad design, this is Adobe not bothering to consider how we want to use our computers. Having said that I use a feature in my Norton anti-virus package to delay the start of the task and will try blocking it completely.īUT why should I as a user have to go to such extreme measures to stop stuff that has no business running in the first place. However the background processes still start automatically and it not obvious where or how it gets activated. ![]() I have the cc control interface set to 'not start on login'. On my system with my usage profile the creative cloud process has nothing to do other than occasionally check that I have an active licence, so why am I burdened with all this other stuff? I expect that as I am not using any features that require Sync that processes such as CoreSync would be switched off and never run at all.Īny why do they not stop when I am not using lightroom etc? How do I get rid of these processes and stop them running? They are certainly irritating me and littering my Temp folder with log files, not to mention adding to the wear and tear of my disk. Note that I am not using any of the cloud features. I find that various background process get started and constantly access my disk even when I am not using and even when I have never started lightroom etc.Īs far as I can determine these processes are doing nothing that is useful to me. I do not use any of the cloud storage services on online resources and have these set to off in the creative cloud desktop interface properties. ![]() 1 release of creative cloud with just lightroom, photoshop and bridge installed. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |