aboutsummaryrefslogtreecommitdiff
path: root/src/feature/dirauth/dirauth_sys.c
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2019-04-26 13:17:35 -0400
committerNick Mathewson <nickm@torproject.org>2019-04-30 11:14:59 -0400
commitb7cc631d2391d55c078e0693303f6a0d4d9e963a (patch)
tree0c50ef90b58c72d89d5eff40e0f9384cc73f74b8 /src/feature/dirauth/dirauth_sys.c
parent9a62a820fb2b0319c27d5f5131c2227a66133ee0 (diff)
downloadtor-b7cc631d2391d55c078e0693303f6a0d4d9e963a.tar.gz
tor-b7cc631d2391d55c078e0693303f6a0d4d9e963a.zip
Rename and clarify some functions for periodic events
When we tell the periodic event manager about an event, we are "registering" that event. The event sits around without being usable, however, until we "connect" the event to libevent. In the end, we "disconnect" the event and remove its libevent parts. Previously, we called these operations "add", "setup", and "destroy", which led to confusion.
Diffstat (limited to 'src/feature/dirauth/dirauth_sys.c')
-rw-r--r--src/feature/dirauth/dirauth_sys.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/feature/dirauth/dirauth_sys.c b/src/feature/dirauth/dirauth_sys.c
index 6845e62c27..bb482f2685 100644
--- a/src/feature/dirauth/dirauth_sys.c
+++ b/src/feature/dirauth/dirauth_sys.c
@@ -14,7 +14,7 @@
static int
subsys_dirauth_initialize(void)
{
- dirauth_add_periodic_events();
+ dirauth_register_periodic_events();
return 0;
}