I’ve been running my own homelab for years, and like many of you, I’ve had my fair share of DNS resolution issues. Last year, I decided to ditch my router as a DNS server and set up Unbound and systemd-resolved on my Linux machines instead. The goal was to improve DNS resolution speed and security, but as you can probably guess, it wasn’t all smooth sailing.
[Read More]As someone who’s spent years running a homelab, I’ve found myself dealing with a multitude of background tasks on a daily basis. These tasks can range from simple scripts to complex services, all of which need to be managed and monitored. I’ve seen this go wrong when a task is left to run without proper management, so I’ve learned to rely on tools like screen and tmux to keep my tasks running. However, I’ve recently started using nohup and systemd to manage my background tasks, and I have to say, it’s been a game-changer.
As someone who’s spent years running a homelab, I’ve learned that managing background tasks can be a real challenge. You’ve got scripts and commands that need to keep running, even after you’ve logged out of your system. In my experience, nohup and systemd have been the two most useful tools for getting this done.
nohup is a simple command that lets you run a process in the background, ignoring the SIGHUP signal that’s sent when the controlling terminal closes. This means you can start a process with nohup, log out, and the process will just keep on running. Here’s an example: