A recent OS upgrade rendered the crontab to malfunction on macOS Monterey. It turned out the system just needed a reset of System Preferences > Security & Privacy > Privacy tab, and to make sure cron has full access to disks. Once you flipped that, your crontab should start working. Hope that helps.
If you have a file with @ sign at end, this is how to remove extended attributes on the Mac OS.
ls -l -rwxr-xr-x@ 4 username staff 128 Mar 24 10:51 sample.txt
Remove extended attributes.
xattr -c sample.txt
ls -l -rwxr-xr-x 4 username staff 128 Mar 24 10:51 sample.txt
I tried running git after the Mac OS Catalina upgrade and got this error.
xcrun: error: invalid active developer path (/Library/Developer/CommandLineTools), missing xcrun at: /Library/Developer/CommandLineTools/usr/bin/xcrun
Here’s the fix. For some very odd reason, Apple does not automatically reinstall xcode after each Mac OS upgrade.
You will need to either reset it or install it again.
# Try reset first xcode-select --reset # Or install it if reset doesn't work xcode-select --install
Close your terminal, and reopen and run git again.
If you’ve recently upgraded your Mac to Catalina or Mac OS 10.15.1, you may have noticed that Audacity is no longer working. To get it working, you’ll need to download version Audacity 2.3.3. However, installing and running it normally the way you’ve done it in the past will not be enough. Because of Catalina, Audacity is not able to gain permissions to the microphone inputs. The only way I was able to get it working is to launch Audacity from the Terminal.
Launch Audacity from the Terminal.
# cd to Application directory cd /Applications/Audacity.app/Contents/MacOS # Run it in the background bash Audacity.sh &
Click Ok if prompted to use the microphone.
I’ve updated my system to the latest Mac OS 10.15.1 codenamed Catalina. Well, it broke a couple of apps that I use regularly, Audacity and OBS. There are currently no updates from Audacity. However, OBS has a workaround in terms of a test build. You have to download it, and set the system preferences to allow the Mac OS to access the cameras (webcam) and audio devices (microphones). There are no official releases yet from neither Audacity and OBS projects. Maybe in a couple of months.
If you’re using Finder on a Mac OS, the quickest way to display and hide hidden files is by using the Command + Shift + . (or the period) key combination. This key combination will toggle on and off the hidden files inside the Finder. By the way, this is only applicable if you have the Mac Sierra OS and above. I like the clean look better (without the hidden files), but the Command + Shift + . is pretty handy if you need to quickly look at hidden files.
I’m thinking about using the Linux desktop again after 4 years of inactivity. The MacOS was the desktop of choice. I’ve been happy with the switch. I don’t anticipate abandoning it any time soon. Lately I thought about sharpening up my Linux skills after having been dormant for years. I need a Linux platform that I can work with. Ubuntu is my default, but there are other distros equally interesting. Mint, Debian and Fedora come to mind. Instead of having multiple boot partitions, I might install Ubuntu as the base distro and install Virtualbox. Other distros can be fired up as virtual machines. In that way, it’s simple to manage. I just need a heftier machine that can handle several VMs running at the same time. That’s the plan for the next several weeks.
If you work on servers via Terminal using SSH (secure shell), one of the more annoying things that happens quite regularly are timeouts. If there’s no activity between your SSH client and the server, your terminal is closed because your session has timed out. You’ll need to login again. If you do this at least 6 times a day, then you can see how taxing this whole exercise can be.
To avoid Terminal timeouts, you can set the SSH client, your terminal, to keep the connection alive by sending a null signal to the server every few seconds. I’ve set mine to 2 minutes. Since I’m on Mac OS, I’ll need to configure my SSH client. The configuration file is located in your home directory under .ssh/config. If the file doesn’t exist, just create one.
cd nano .ssh/config
Now add the following lines to it.
Host * ServerAliveInterval 120
I’ve set mine to 120 seconds or 2 minutes. This value works for me while connected to an Ubuntu Server. You may have to play around with this value on other Linux systems. I think this is a better approach as opposed to configuring the SSH server on every server you are connected to. You may not have root access to some servers. Changing the settings on your SSH client is the better approach.