From 7f33ccb920df2c308aa3076522bea683c66cb83d Mon Sep 17 00:00:00 2001 From: Matthias Schiffer Date: Thu, 29 Aug 2013 19:04:31 +0200 Subject: Don't initialize monotone timestamps with zero The monotone timestamp is near zero on linux systems, confusing fastd. --- src/peer.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'src/peer.c') diff --git a/src/peer.c b/src/peer.c index a9c3415..5c30307 100644 --- a/src/peer.c +++ b/src/peer.c @@ -201,16 +201,16 @@ static void setup_peer(fastd_context_t *ctx, fastd_peer_t *peer) { fastd_remote_t *remote; for (remote = peer->remotes; remote; remote = remote->next) { - remote->last_resolve = (struct timespec){0, 0}; - remote->last_resolve_return = (struct timespec){0, 0}; + remote->last_resolve = ctx->conf->long_ago; + remote->last_resolve_return = ctx->conf->long_ago; } peer->next_remote = peer->remotes; - peer->last_handshake = (struct timespec){0, 0}; + peer->last_handshake = ctx->conf->long_ago; peer->last_handshake_address.sa.sa_family = AF_UNSPEC; - peer->last_handshake_response = (struct timespec){0, 0}; + peer->last_handshake_response = ctx->conf->long_ago; peer->last_handshake_response_address.sa.sa_family = AF_UNSPEC; if (!peer->protocol_state) -- cgit v1.2.3