I’ve worked with systemd services for years, and one thing that’s always caught my attention is the Restart directive. You know, that option that lets you configure how a service should be restarted in case of failure. The RestartSec option is particularly interesting - it specifies the time to sleep before restarting a service. But, as I’ve learned the hard way, RestartSec isn’t always enough to ensure reliable service restarts.
I’ve seen this go wrong when working with systemd services: a service restarts repeatedly, causing issues with your system’s stability and performance. The real trick is to understand how to tame this behavior using two key parameters: StartLimitBurst and StartLimitInterval.
These two settings are related and determine how often a systemd service can restart within a given time frame. StartLimitBurst specifies the maximum number of restarts allowed within the StartLimitInterval time period. If the service restarts more times than specified by StartLimitBurst within the StartLimitInterval, it will be placed in a failed state and will not be restarted again.