On Fri, Feb 17, 2017 at 01:20:59PM +0100, Sandro Stiller wrote: > > Does it not log anything anymore after those messages? Or does it > > continue giving the "Error looking up..." message periodically? > > It stops working completely. > > > In the first case, try sending tinc the ALRM and/or HUP signal (tincd -n > > <netname> -kALRM). This should cause tinc to retry outgoing connections > > immediately. > > After that, it continues trying. > > I think, I found the cause of the problem: > Is tinc using a monotonic / steady clock for timeouts or is it using the > system time?
I think you are right! It uses time() and gettimeofday() to calculate
how long to wait for the timeouts. I'll have to look at a portable way
to get a monotonic clock.
> > In any case, which Linux distribution are you using?
>
> It's an OpenEmbedded-based distribution for embedded devices
Ok, that probably explains why you always have a large jump in time at
boot. Just curious: what hardware are you running tinc on?
The best solution for now is to send tinc an ALRM signal after the time
is set.
--
Met vriendelijke groet / with kind regards,
Guus Sliepen <[email protected]>
signature.asc
Description: Digital signature
_______________________________________________ tinc mailing list [email protected] https://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
