Automating Server Tasks with Systemd Timers is a common requirement for VPS administrators. This guide provides practical instructions that you can follow on Ubuntu 22.04/24.04 or Debian 12, though most steps apply to other distributions as well.
Initial Setup
Before making changes to the configuration, always create a backup of the existing files. This ensures you can quickly roll back if something goes wrong during the setup process.
# Systemd service management
sudo systemctl status nginx
sudo systemctl enable --now nginx
sudo systemctl restart nginx
# View service logs
sudo journalctl -u nginx -f --since "10 minutes ago"
# List all running services
systemctl list-units --type=service --state=running
The output should show the service running without errors. If you see any warning messages, address them before proceeding to the next step.
- Maintain runbooks for common operations
- Set up monitoring before going to production
- Use version control for configuration files
- Document all configuration changes
Configuration Steps
Performance benchmarks show that properly tuned systemd can handle significantly more concurrent connections than the default configuration. The key improvements come from adjusting worker processes and connection pooling.
# Server resource monitoring
htop # Interactive process viewer
iostat -x 1 5 # Disk I/O stats (5 samples)
vmstat 1 5 # Virtual memory stats
ss -tlnp # Open listening ports
netstat -an | wc -l # Total connections
This configuration provides a good balance between performance and resource usage. For high-traffic scenarios, you may need to increase the limits further.
Wrapping Up
Following this guide, your systemd setup should be production-ready. Keep an eye on resource usage as your traffic grows and don't forget to test your backup and recovery procedures periodically.