Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

systemd service: restart less agressively but still quicker #13502

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

systemd service: restart less agressively but still quicker #13502

wants to merge 1 commit into from

Commits on Nov 16, 2023

  1. systemd service: restart less agressively but still quicker 

    If a service fails to start because it's not properly configured (e.g.
directly after installation) the existing settings make the daemons
restart in a loop. Each start logs several lines to the journal
which quickly results in older but probably still relevant logs of other
serives being rotated out.

Dropping RestartSec makes systemd use the default of 100ms. So a restart
happens quicker. With dropping StartLimitInterval=0 systemd applies some
ratelimiting and (by default) only starts the service 5 times per 10s.

Replacing Restart=on-failure by Restart=on-abnormal makes systemd not
restart the service if the daemon process exits with a non-zero exit
code. It's still restarted when the process exits by a signal (other
than SIGHUP, SIGINT, SIGTERM or SIGPIPE).

Debian-Bug: https://bugs.debian.org/1055529
    @ukleinek
    ukleinek committed Nov 16, 2023
    Configuration menu
    Copy the full SHA
    67f9263 View commit details
    Browse the repository at this point in the history