Troubleshooting is often a process of elimination and does require patience, so you'll need to keep that in mind as you proceed.
The first thing I would do now is test your Mac in Safe Mode.
Boot into Safe Mode
Follow these steps to boot your Mac into Safe Mode:
Fully shut down your Mac
Restart your Mac
Immediately press the Shift key and keep it down
I'm posting this as a separate answer since I did not have to fiddle with any plist files to make this work.
Here's how I installed and started CNTLM today:
Install CNTLM with Homebrew
brew install cntlm
Edit CNTLM configuration
Edit the /usr/local/etc/cntlm.conf file, update the following items:
Username: The user name for authenticating with your NTLM ...
Pierz' * solution worked, and seems the best, for me. (I quote it more or less verbatim because I don't have enough reputation to just comment)
Copy the disabled plist file from /System/Library to /Library:
sudo cp /System/Library/LaunchDaemons/org.ntp.ntpd-legacy.plist /Library/LaunchDaemons/
Edit the new file to un-disable the job. I.e. remove both ...
I overcame the issue by creating an application wrapper for the script using Platypus - https://sveinbjorn.org/platypus.
I gave the resultant app Full Disk Access in the Privacy pref pane and this allowed it to run.
(Any subsequent change to the core script means regenerating the app and removing and re-adding it in Privacy as the new file is not ...
I want to view the status of a service in macOS using launchctl
to view the status, use print: launchctl print system/org.apache.httpd
Syntax is: launchctl print <domain>/<item>
Domain can be:
Various combinations and examples below:
A fresh system install, with default parameters is configured with the following system wide file limits:
Kernel Max Files: 12288
Max Files per Process: 10240
Current kernel sysctl parameters can be viewed with sysctl command:
$ sysctl -a |grep kern.maxf
Now let's check limits values, using ulimit command:...
LaunchAgents are basically the same as LaunchDaemons, except that:
LaunchAgents runs only after the user Logs in, process runs on the Logged in UID (User ID) with the logged user privileges. Process can interact with the logged user via GUI.
LaunchDaemons runs on boot time, before the GUI is up, during the progress bar on the boot screen. It run as root, ...
You can't use $HOME in the plist but you can configure it easily enough.
Once the plist is loaded on the proper computer (lets assume it is at ~/Library/LaunchAgents/local.testing.plist for the sake of discussion)
All you need to do is enter two commands at the command line
defaults write "$HOME/Library/LaunchAgents/local.testing.plist" \
You cannot use $HOME in these keys. You'll need to use the work-around shown in this answer:
how can I use $HOME, ~ or environment variable in plist file of LaunchDaemons
And then use ordinary shell scripting to redirect standard out and standard error to locations within $HOME. I.e. use a command similar to:
command >$HOME/launchd.stdout.log 2>$...
The standard Apache is started through /System/Library/LaunchDaemons/org.apache.httpd.plist:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">