Searched refs:nextdate (Results 1 – 8 of 8) sorted by relevance
2460 peer->nextdate++; in receive()2462 peer->nextdate--; in receive()3062 peer->nextdate = utemp; in poll_update()3072 peer->nextdate = utemp; in poll_update()3074 peer->nextdate = utemp; in poll_update()3123 peer->nextdate = next; in poll_update()3125 peer->nextdate = utemp; in poll_update()3131 if (peer->nextdate > limit) { in poll_update()3133 limit, peer->nextdate)); in poll_update()3134 peer->nextdate = limit; in poll_update()[all …]
338 if (p->nextdate <= current_time) { in timer()
1690 if (peer->nextdate <= limit) in refclock_checkburst()1712 peer->nextdate = limit; in refclock_checkburst()
1085 peer->nextdate = current_time + 10; in chu_burst()
1043 ip->timetosend = htonl(pp->nextdate - current_time); in peer_stats()
2746 p->nextdate - current_time); in ctl_putpeer()
389 u_long nextdate; /* send time next packet */ member
987 (poll_update): peer->nextdate, not ->outdate. More cleanup around1397 (poll_update): Poll wiggles. Make sure peer->nextdate is timely.2413 * ntpd/ntp_peer.c (newpeer): Better nextdate choice.5492 (acts_receive): Update peer->nextdate with current_nextdate