Taming Background Tasks with nohup and systemd: My Homelab Workflow

 Posted on 20 July 2026  |  3 minutes  |  498 words  |  Tom

Introduction to Background Tasks

I’ve been running Linux servers in my homelab for years, and one thing that’s always come up is the need to run background tasks. These can be anything from simple scripts to complex applications, and they need to keep running even when I log out. I used to rely on tools like screen and tmux, but lately, I’ve been using nohup and systemd to simplify things.

Using nohup

nohup is a command that lets you run a process in the background, ignoring hangup signals. So, even if you log out, the process will keep running. To use it, you just prefix your command with nohup and add an ampersand (&) at the end. For example:

nohup ./my_script.sh &

This runs my_script.sh in the background, and it’ll keep going even if you log out. You can use nohup with other commands like python or java to run applications in the background. The real trick is to make sure your script or application can handle being run in the background.

Using systemd

While nohup is simple and effective, it’s not always the best choice. If you need to run a task at startup or manage multiple tasks, systemd is a better option. systemd is a system and service manager that lets you create and manage services on your Linux system. To create a systemd service, you need to create a service file in the /etc/systemd/system directory. For example, you could create a file called my_service.service with the following contents:

[Unit]
Description=My Service
After=network.target

[Service]
User=myuser
ExecStart=/path/to/my/script.sh
Restart=always

[Install]
WantedBy=multi-user.target

This tells systemd to run my_script.sh as the myuser user and restart the service if it fails. Then, you can enable and start the service with:

sudo systemctl enable my_service
sudo systemctl start my_service

If you want to learn more about systemd, the systemd.io website is a great resource. Don’t bother with the man pages unless you’re really stuck - the website has better documentation.

Trade-offs and Considerations

When deciding between nohup and systemd, there are some trade-offs to consider. nohup is easy to use, but it doesn’t give you the same level of control as systemd. On the other hand, systemd requires more setup, but it’s way more flexible. In practice, I usually start with nohup for simple tasks, but if I need more control or features, I switch to systemd. This is where people usually get burned - they try to use nohup for complex tasks and end up with a mess.

Troubleshooting

If you’re having trouble with nohup or systemd, there are a few things to try. First, make sure you’re using the right syntax and options. Check the man page if you need to, but like I said, the systemd website is usually a better bet. If you’re still stuck, try checking the system logs with journalctl to see if there are any error messages or warnings. I’ve seen this go wrong when people don’t configure their services correctly, so double-check your setup.

linux  systemd  background-tasks 

See also