Dec 13, 2013  Adobe Distiller creates log files. Have you tried looking at the Liquid Office server? Many servers create log files to help administrators track down problems, perform an incremental restore, etc. Step 1: Modify the hosts file to block all outgoing connect to Adobe server– From the Desktop, press Command + Shift + G, type /etc into the field then hit Enter.– Locate the hosts file, remove all lines that contain “xxx. If you block it by deleting the LOG files then it plays the 'not responding' notice and recreates the LOG files in the Temp Folder. The three LOG files in the Temp folder that are recreated even if you delet them or rename them are alm.log, amt.log and swtag.log.

How do I stop the Adobe Creative Cloud app from auto-launching on login? I don't see any option of stopping this, and for some reason it's not in OS X's user login options.

Adobe Acrobat Log Files

4 Answers

It is loaded by default by /Library/LaunchAgents/com.adobe.AdobeCreativeCloud.plist.

If you run

that will disable it for your user.

To turn it back on

1. Click on the menu bar icon.

2. Click the ellipsis icon at the top-right.

3. Select “Preferences”

4. Uncheck “Launch at login”.

5. Note: The “Preferences” option does not appear until you log in to Creative Cloud.

To turn off everything Adobe launches at startup on the Mac you need to both disable its launchd jobs and the Adobe Core Sync extension.

For the Adobe Core Sync extension, it is a Finder Sync extension so you can disable it under System Preferences → Extensions as described in this answer - https://apple.stackexchange.com/a/237585/23876. From what I have seen, you will need to repeat this step after each Adobe Creative Cloud upgrade.

For the launchd jobs, read on. Note that the following will also disable Adobe automatic update checking. So you will need to check for updates from inside one of the Adobe apps or explicitly run Adobe Create Cloud.

Adobe actually puts their launchd job definitions in several places and those places change depending on the Adobe version. Building on @Alan Shutko’s answer, the following will disable them everywhere. You can ignore any “Could not find specified service” warnings. After running, reboot to enjoy an Adobe free launch (until you actually run an Adobe product).

As background, launchctl unload -w disables each service in the override database. launchd will follow the override database entry even if the job definition (e.g. /Library/LaunchAgents/com.adobe.AdobeCreativeCloud.plist) is marked as enabled. The override database is on a per user basis. LaunchDaemon jobs are run as root so we use sudo to disable them for the root user.

From what I have seen so far, Adobe installs do not update the override database, so you shouldn't need to run the commands again after an Adobe install (unless they introduce another job). Please comment if someone does see Adobe touching the override database.

For more information on launchd, the launchd Tutorial is a great overview on launchd jobs. And LaunchControl is a good tool for working with launchd jobs. LaunchControl is a paid app, but the trial version supports viewing them. Be sure to enable tooltips so you can see the override database values.

I'm currently using this set of commands—the wildcard answer will be a bit more future-proof if Adobe adds more services, but:

1. Apple is shifting to having these services embedded inside app bundles, so new services added by Adobe may not appear in the usual /Library/Launch*/ paths but still have the same infuriating launch-at-login behavior and
2. this answer lets you target a single user (if you have multiple users on your machine) for the Creative Cloud UI and sync daemon, should you wish to leave them in place for another person.

You must log in to answer this question.

protected by Community♦Aug 4 '15 at 14:23

Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?

Not the answer you're looking for? Browse other questions tagged adobelogin-items .

Related Articles

• 1 Make Yourself an Administrator From the Terminal on a Mac
• 2 Have Chrome for Mac Not Automatically Update
• 3 Edit the Mailbox on a BlackBerry Bold
• 4 Configure GroupWise on Android

Windows 10 Iso File For Mac

The built-in Mac OS X firewall provides the ability to block incoming connections, but it doesn't provide a transparent way to block outgoing connections. However, you can use Terminal to set your Mac to block connections for specified programs. The 'hosts' file contains the firewall settings for your Mac. Using Terminal you can access the file and make changes to your firewall settings to block access to specific websites and prevent information from leaving your network.

Click the 'Go' menu, select 'Utilities,' and then double-click 'Terminal' to launch the utility.

Type 'sudo cp /private/etc/hosts ~/Documents/hosts-backup' (omit the quotes here and throughout) to create a backup of the 'hosts' file before editing. You can open this file later if you find the changes you made to your system resulted in unintended behaviors.

Type 'sudo nano /private/etc/hosts' in the Terminal window, and then press the 'Enter' key. 'Sudo' indicates that you want to gain administrator access, 'nano' tells Terminal the program to use -- in this case, the Nano text editor -- and the pathname indicates the location of the 'hosts' file.

Type your administrator account password, and then press the 'Enter' key. You must set up a password for your account to make changes in Terminal. If your account doesn't have a password, select 'System Preferences' in the Dock, click 'Users & Groups,' select your administrator account, click the 'Change Password...' button, and then enter a new password.

Press the down arrow key to position the cursor below the default set of rules. Don't edit any of the existing rules as they set your current firewall settings and allow your computer to function properly.

Type the domain IP address of the website you want to block communication with in a blank line followed by a space and the domain name. Use the format '0.0.0.0 domainname.com' and put each entry on a separate line.

Close the window, enter the Terminal application again, and then type 'dscacheutil -flushcache' to reset the cache and apply the new rules.

Tip

• If you don't feel comfortable using Terminal to make changes, consider using one of the free firewall programs like Little Snitch, WaterRoof or NoobProof (links in Resources). These applications provide a user-friendly interface that allows you to easily disable outgoing applications for specific applications or all network activity. Little Snitch works well if you're an advanced user who wants to monitor all incoming and outgoing connections in real-time. WaterRoof provides options if you want to keep the OS X firewall active and still use advanced rules to configure dynamic rules, NAT and port-forwarding, bandwidth managers and other options. NoobProof provides a user-friendly approach without many of the advanced options available in WaterRoof.

Warning

• Information in this article applies to OS X Mountain Lion. It may vary slightly or significantly with other versions of OS X.

About the Author

Avery Martin holds a Bachelor of Music in opera performance and a Bachelor of Arts in East Asian studies. As a professional writer, she has written for Education.com, Samsung and IBM. Martin contributed English translations for a collection of Japanese poems by Misuzu Kaneko. She has worked as an educator in Japan, and she runs a private voice studio out of her home. She writes about education, music and travel.

Photo Credits

• Kimberly White/Getty Images News/Getty Images

Choose Citation Style