Skip to content

htpdate.service is always started

boyska requested to merge 18868-htpdate-start-from-systemd into testing

the service is still smart enough to wait for Tor bootstrap itself. The only reason it would make sense to wait for TCA to have done its job, is for the notification.

You might wonder: why should we start htpdate.service from a NetworkManager hook, instead of systemd? I wanted to be sure that at every reconnection, htpdate was restarting. So if a user is disconnecting from wi-fi, then connecting again, htpdate will be started again.

This MR also adds a regression test. The regression test is very slow (it even needs to be very slow!), so it's not run in most cases.

Closes #18868 (closed)

Things to check:

  • are we running all tests that we expect to? ie. is our --tag sequence right?
  • is the behavior correct in the case of disconnect and reconnect to the network?
Edited by intrigeri

Merge request reports