Skip to content

Commit

Permalink
main/chrony: make the 3 minute timeout "successful"
Browse files Browse the repository at this point in the history
If there is no sync after 3 minutes, we should consider chrony
started (the wait only exists so that time-sync.target can be
considered somewhat reliable, but it should not wait forever).
Still have a bigger hard timeout just in case (if that hits,
something has really gone wrong and stopping chronyd is the
right thing to do).
  • Loading branch information
q66 committed Dec 31, 2023
1 parent c67f616 commit 1e4d371
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 3 deletions.
4 changes: 2 additions & 2 deletions main/chrony/files/chrony
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
# wait for time to be synchronized

type = scripted
command = /usr/bin/sh -c "/usr/bin/chronyc -h 127.0.0.1,::1 waitsync 0 0.1 0.0 1 || :"
start-timeout = 180
command = /usr/bin/sh -c "/usr/bin/chronyc -h 127.0.0.1,::1 waitsync 180 0.1 0.0 1 || :"
start-timeout = 240
depends-on = chronyd
before = time-sync.target
options = start-interruptible
2 changes: 1 addition & 1 deletion main/chrony/template.py
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
pkgname = "chrony"
pkgver = "4.5"
pkgrel = 1
pkgrel = 2
build_style = "gnu_configure"
configure_args = [
"--with-user=_chrony",
Expand Down

0 comments on commit 1e4d371

Please sign in to comment.