

- #Mac os x shell script remove applications launchagent install#
- #Mac os x shell script remove applications launchagent software#
To make things easy for the average user who is not necessarily familiar with the command line, we wrote one single install script that sets up DeamonLeash for you. DaemonLeash consists of a Launch Daemon, a Launch Agent, four Shell Scripts and a Log File. Our script uses much less CPU power than the average Adobe background process. However we added Google Chrome as an example to show how DaemonLeash could be configured to target other background processes as well. We recommend you use Mozilla Firefox or the Tor Browser. We did not implement a backgound listener for Google Processes, because we don't use Google Chrome. It also keeps listening in the background while you are using your favorite Adobe Application and terminates any persitent Adobe Backgound Process as soon as you finish actively using the software. Whenever you start your computer DaemonLeash checks for both Adobe and Google Launch Daemons and disables them before they can connect to the internet. We want to limit the collection of our data as much as we can.
#Mac os x shell script remove applications launchagent software#
Yet we think it already is intolerable that Adobe and Google automatically know when, where and for how long we use our computers just because we have their software installed on our system. Adobe claims only to collect data to improve its products.

The average user does not exactly know what data is being collected by big Software Corporations, even though i.e. Yes, background processes check for updates too - yet we prefer to check for updates manually.īut most importantly we do value our privacy. These processes require processing power that we want to use in other ways. Google Chrome does behave exactly the same way. We have been using Adobe Creative Cloud (for Mac OSX) for quite a while now and it came to our attention that several background processes connect to Adobe Servers to send out data as soon as we start our Computer (even though we did not start any Adobe Application). Adobe might have changed its LaunchDeamons and this script might not catch them anymore. A word in advance: we stopped using Adobe a while ago and we found software alternatives for all our needs, which is why we also stopped to maintain this script.
