Atom Uninstall

No, the Atom text editor does not have an uninstaller. On Mac OS X, to completely uninstall, remove the following files and directories: ~/.atom /usr/local/bin/atom (NB only present if command line tools installed) /usr/local/bin/apm (NB only present if command line tools installed) /Applications/ ~/Library/Application Support/ ~/Library/Preferences/com.github.atom.plist ~/Library/Application Support/com.github.atom.ShipIt ~/Library/Application Support/Atom ~/Library/Caches/com.github.atom.ShipIt/ ~/Library/Saved Application State/com.github.atom.savedState ~/Library/Logs/Atom/ ~/Library/Preferences/com.github.atom.helper.plist ~/Library/Preferences/com.github.atom.LSSharedFileList.plist ~/Library/Preferences/ByHost/com.github.atom.ShipIt.<letters/numbers>.plist ~/Library/Saved Application State/com.github.atom.savedState NB: The <letter/numbers> in the file name located in ~/Library/Preferences/ByHost appear to be a unique string per machine.

Thoughts on the Atom Editor

I installed the Atom text editor quite a while ago and didn’t have much time to play around with it. Last week a friend of mine brought it up in conversation. She was extolling its virtues. I decided now would be a good time to try it out. I was moving a site to Hugo and it has a plugin for Hugo syntax. So I fired it up and, my word, a decade later an editor window opened.

Deprecated nf_conntrack automatic helper assignment

For quite a while, I’ve been getting the “nf_conntrack: automatic helper assignment is deprecated and it will be removed soon” warning at boot. So I can’t say I was too surprised when I started getting “kernel: nf_conntrack: default automatic helper assignment has been turned off for security reasons and CT-based firewall rule not found. Use the iptables CT target to attach helpers instead.” Back in January/February 2017 there was a post on the Linux-Kernel mailing list submitting a patch to print out the warning so firewall admins would at least have notice.

Nginx, OCSP stapling, booting, systemd and Debian 9

Noticed these lines in journalctl when nginx didn’t start after a reboot: Dec 10 17:43:30 mail1 nginx[3485]: nginx: [warn] "ssl_stapling" ignored, host not found in OCSP responder "" in the certificate "/etc/letsencrypt/live/" Dec 10 17:43:30 mail1 nginx[3485]: nginx: [emerg] bind() to [<IPv6 address>]:80 failed (99: Cannot assign requested address) Dec 10 17:43:30 mail1 nginx[3485]: nginx: configuration file /etc/nginx/nginx.conf test failed Dec 10 17:43:30 mail1 systemd[1]: nginx.service: Control process exited, code=exited status=1 Dec 10 17:43:30 mail1 systemd[1]: nginx.

Script: Update Linode DNS Records with WAN IPs (Dynamic DNS)

Either of these scripts will grab both the IPv4 and IPv6 (if any) addresses assigned to any WAN I’m behind, and, using Linode’s DNS API, will update my DNS records with same and log changes/errors using logger. In effect, it’s a homemade Dynamic DNS updater. Linode’s developing a new API so that’s why two versions exist. Download from Bitbucket To use the script, you need: A Linode API key (for version 3 of Linode’s DNS API) or Personal Access Token (for version 4 of Linode’s DNS API), the domain ID, and the resource (called record in v4) IDs of the DNS records you want to update.