linux

4 posts with the tag “linux”

Automating Homelab Tasks with Cron

Jun 6, 2026

Automating Homelab Tasks with Cron

In a homelab, there are many tasks that benefit from automation: backups, log rotation, system updates, or even just checking the status of services. cron is the classic Unix utility for scheduling commands to run periodically. This post will guide you through setting up and managing cron jobs.

Tip

cron is incredibly powerful but can be tricky. Always test your cron jobs thoroughly in a safe environment before deploying them to critical systems.

Understanding Cron Syntax

A cron job entry (a “crontab” entry) consists of five time fields followed by the command to be executed. The fields are:

* * * * * command-to-be-executed
- - - - -
| | | | |
| | | | ----- Day of week (0 - 7) (Sunday=0 or 7)
| | | ------- Month (1 - 12)
| | --------- Day of month (1 - 31)
| ----------- Hour (0 - 23)
------------- Minute (0 - 59)

Special Strings

For common schedules, cron offers special strings:

String	Description	Equivalent
@reboot	Run once after reboot	N/A
@yearly	Run once a year	0 0 1 1 *
@annually	Same as @yearly	0 0 1 1 *
@monthly	Run once a month	0 0 1 * *
@weekly	Run once a week	0 0 * * 0
@daily	Run once a day	0 0 * * *
@midnight	Same as @daily	0 0 * * *
@hourly	Run once an hour	0 * * * *

Managing Cron Jobs

Editing Your Crontab

Each user has their own crontab. To edit it, use:

crontab -e

This will open your crontab in a text editor (usually nano or vim). Add your job entries at the end of the file.

Listing Cron Jobs

To view your current cron jobs:

crontab -l

Removing Cron Jobs

To remove all your cron jobs:

crontab -r

Caution

crontab -r removes all jobs without confirmation. Use crontab -e to selectively delete entries.

Practical Examples

Daily Backup Script

Let’s say you have a backup script at /usr/local/bin/backup-homelab.sh. To run it every day at 2:00 AM:

0 2 * * * /usr/local/bin/backup-homelab.sh >> /var/log/homelab-backup.log 2>&1

• 0: Minute 0
• 2: Hour 2 (2 AM)
• *: Every day of the month
• *: Every month
• *: Every day of the week
• >> /var/log/homelab-backup.log 2>&1: Redirects both standard output and standard error to a log file.

Hourly System Update Check

To check for system updates every hour:

0 * * * * sudo apt update > /dev/null 2>&1

• 0: Minute 0
• *: Every hour
• > /dev/null 2>&1: Discards all output to prevent excessive emails from cron.

Reboot Task

Run a script once after every system reboot:

@reboot /usr/local/bin/start-homelab-services.sh

Environment Variables in Cron

Cron jobs run with a minimal set of environment variables. If your script relies on specific PATH settings or other variables, you need to define them within the crontab or explicitly in your script.

PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
0 3 * * * /usr/local/bin/my-script.sh

Alternatively, specify the full path to all commands in your script.

Troubleshooting Cron Jobs

Issue	Possible Cause	Solution
Job not running	Incorrect time syntax, script path	Check crontab -l, verify script path
Job fails silently	Environment variables, permissions	Redirect output to a log file, check script permissions (chmod +x)
No output	Output redirected to /dev/null	Remove redirection temporarily to debug
Email spam	Job produces output	Redirect output to /dev/null or a log file

Checking Cron Logs

Cron activity is often logged in /var/log/syslog or /var/log/cron.

sudo grep CRON /var/log/syslog

Best Practices

1. Use full paths: Always specify the full path to commands and scripts (e.g., /usr/bin/python3 instead of python3).
2. Log output: Redirect output to a log file (>> /path/to/log.log 2>&1) to capture errors and verify execution.
3. Test scripts: Run your scripts manually from the command line before adding them to cron.
4. Minimal privileges: Run cron jobs as the user with the least necessary privileges.
5. Comments: Add comments to your crontab (# This is a comment) to explain complex entries.

Conclusion

cron is a robust and reliable tool for automating tasks on your homelab. By understanding its syntax and following best practices, you can free yourself from repetitive manual work and ensure your systems are maintained efficiently.

Automate responsibly!

Tags:

• homelab
• linux
• automation

Essential Linux Commands for Developers

Jun 4, 2026

Essential Linux Commands for Developers

Working in software development often means spending a lot of time in the terminal, especially on Linux systems. Mastering a few essential commands can significantly boost your productivity. Here’s a quick reference guide to some of the most useful ones.

Tip

Practice these commands regularly. Muscle memory in the terminal is a huge time-saver!

File System Navigation and Manipulation

Command	Description	Example Usage
ls	List directory contents	ls -la (long format, all files)
cd	Change directory	cd ../projects/my-app
pwd	Print working directory	pwd
mkdir	Create directory	mkdir new-feature
rm	Remove files or directories	rm -rf old-logs/ (force, recursive)
cp	Copy files or directories	cp -r src/ build/
mv	Move or rename files/directories	mv old-name.txt new-name.md
find	Search for files in a directory hierarchy	find . -name "*.js"

Viewing and Editing Files

Command	Description	Example Usage
cat	Concatenate and display file content	cat README.md
less	View file content page by page	less /var/log/syslog
head	Display first N lines of a file	head -n 10 config.yaml
tail	Display last N lines of a file	tail -f access.log (follow changes)
grep	Search for patterns in files	grep -r "error" . (recursive search)
nano / vim	Text editors	nano script.sh

Process Management

Command	Description	Example Usage
ps	Report a snapshot of current processes	`ps aux
top / htop	Display Linux processes dynamically	htop (more user-friendly)
kill	Send a signal to processes	kill 12345 (terminate process ID 12345)
killall	Kill processes by name	killall node
systemctl	Control the systemd system and service manager	sudo systemctl status nginx

System Information

Command	Description	Example Usage
df	Report file system disk space usage	df -h (human-readable)
du	Estimate file space usage	du -sh my-project/ (summary, human-readable)
free	Display amount of free and used memory	free -h
uname	Print system information	uname -a (all information)
lscpu	Display CPU architecture information	lscpu

Networking

Command	Description	Example Usage
ip addr	Display IP addresses and network interfaces	ip addr show eth0
ping	Send ICMP ECHO_REQUEST to network hosts	ping google.com
curl	Transfer data from or to a server	curl -I https://codevibr.dev (show headers)
wget	Non-interactive network downloader	wget https://example.com/file.zip
ssh	OpenSSH remote login client	ssh user@remote-host

Permissions

Understanding file permissions is crucial for security and proper application function.

# View permissions
ls -l my-file.sh

# Change permissions (read, write, execute for owner, group, others)
chmod 755 my-file.sh

# Change ownership
sudo chown user:group my-file.sh

Package Management (Debian/Ubuntu)

Command	Description	Example Usage
apt update	Refresh package lists	sudo apt update
apt upgrade	Upgrade installed packages	sudo apt upgrade -y
apt install	Install new packages	sudo apt install git
apt remove	Remove packages	sudo apt remove htop

Version Control (Git)

While not strictly a Linux command, Git is indispensable for developers.

# Initialize a new repository
git init

# Clone a repository
git clone https://github.com/user/repo.git

# Check status
git status

# Add changes to staging area
git add .

# Commit changes
git commit -m "feat: add new feature"

# Push changes to remote
git push origin main

Conclusion

This is just a starting point. The Linux terminal is a powerful environment, and there’s always more to learn. The best way to get comfortable is to use it daily. Experiment, read man pages (man <command>), and don’t be afraid to break things in a safe environment.

Happy coding!

Tags:

• linux
• development
• terminal

Homelab Networking Basics

Jun 3, 2026

Homelab Networking Basics

Networking can seem daunting, but for a homelab, understanding a few core concepts will get you a long way. This post covers the essentials: IP addresses, subnets, and basic firewall rules.

Tip

Even if you plan to use a managed router, knowing these basics helps you troubleshoot and configure your devices more effectively.

IP Addresses: Your Device’s Identity

An IP address is like a street address for your device on a network. There are two main types you’ll encounter:

• IPv4: The most common, looks like 192.168.1.100. It’s a 32-bit number.
• IPv6: The newer standard, looks like 2001:0db8:85a3:0000:0000:8a2e:0370:7334. It’s a 128-bit number, designed to address the exhaustion of IPv4 addresses.

Most homelabs still primarily use IPv4, often with private IP address ranges (e.g., 192.168.0.0/16, 172.16.0.0/12, 10.0.0.0/8) that are not routable on the public internet.

Checking Your IP Address

On a Linux machine, you can check your IP address with ip addr:

ip addr show eth0

Example output:

2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:11:22:33:44:55 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.100/24 brd 192.168.1.255 scope global dynamic eth0
       valid_lft 86077sec preferred_lft 86077sec
    inet6 fe80::211:22ff:fe33:4455/64 scope link
       valid_lft forever preferred_lft forever

Here, 192.168.1.100 is the IPv4 address, and /24 indicates the subnet mask.

Subnets: Dividing Your Network

A subnet divides a larger network into smaller, more manageable segments. The subnet mask determines which part of an IP address identifies the network and which part identifies the host.

IP Address	Subnet Mask	Network Address	Host Address
192.168.1.100	255.255.255.0	192.168.1.0	0.0.0.100
10.0.0.50	255.255.0.0	10.0.0.0	0.0.0.50

In CIDR notation, /24 means the first 24 bits are for the network, and the remaining 8 bits are for hosts. This allows for 254 usable IP addresses (2^8 - 2).

Why Subnet?

• Organization: Group devices logically (e.g., servers, IoT, guests).
• Security: Isolate sensitive devices from less secure ones.
• Performance: Reduce broadcast traffic within segments.

Firewalls: Your Network’s Gatekeeper

A firewall controls incoming and outgoing network traffic based on predefined security rules. For Linux, ufw (Uncomplicated Firewall) is a user-friendly interface for iptables.

Basic UFW Commands

# Deny all incoming, allow all outgoing by default
sudo ufw default deny incoming
sudo ufw default allow outgoing

# Allow SSH (port 22)
sudo ufw allow ssh

# Allow HTTP (port 80) and HTTPS (port 443)
sudo ufw allow http
sudo ufw allow https

# Enable UFW
sudo ufw enable

# Check status
sudo ufw status verbose

Caution

Always allow SSH before enabling UFW if you are connected remotely, otherwise you will lose access to your server!

Example Scenario: Web Server

Let’s say you have a web server running on your homelab at 192.168.1.10 and you want to allow external access to it on ports 80 and 443.

sudo ufw allow from any to 192.168.1.10 port 80 proto tcp
sudo ufw allow from any to 192.168.1.10 port 443 proto tcp
sudo ufw reload

This explicitly allows traffic to those ports on that specific IP address.

Next Steps

With these basics, you can start planning your homelab network. Consider drawing a simple network diagram to visualize your devices and their IP addresses. As you grow, you might explore:

• VLANs for advanced network segmentation
• VPNs for secure remote access
• DNS servers for local name resolution

Happy homelabbing!

Tags:

• homelab
• networking
• linux

Homelab Notes Coming Soon

Jun 1, 2026

A short temporary post for testing tags, dates, code blocks, and the rhythm of casual technical writing.

Tags:

• homelab
• linux