[RTEMS Project] #2870: Select and port NTP client (ntpd)

RTEMS trac trac at rtems.org
Wed Jan 18 15:19:22 UTC 2017

#2870: Select and port NTP client (ntpd)
 Reporter:  sebastian.huber  |       Owner:
     Type:  enhancement      |      Status:  new
 Priority:  normal           |   Milestone:  5.0
Component:  General          |     Version:  4.11
 Severity:  normal           |  Resolution:
 Keywords:                   |

Comment (by joel.sherrill):

 Replying to [comment:2 sebastian.huber]:
 > How does Classic NTP work without adjtimex() or ntp_adjtime() system

 In the dark ages of the last century when I ported it, it used adjtime.
 One of the things Harlan wanted to do was improve the interface to RTEMS.
 But we also needed work. With the many changes to RTEMS, it may be easier
 to do than when we discussed this.

 > The reference implementation is the one from [http://www.ntp.org] which
 should be [https://svnweb.freebsd.org/base/head/contrib/ntp/].

 This is what Chris and I refer to as NTP Classic. It was used as the
 starting point for NTPsec. IMO NTPsec started out in the right direction
 by updating to C99 and POSIX 2001. They dropped support for any target not
 available/supported for over a certain length of time. That significantly
 reduced the code base without altering the design of the reference
 implementation (e.g. NTP Classic). Then they decided to start making
 technical changes and switched from the multi-threaded model in NTP
 Classic to libevent. Email Chris and I for more details.

Ticket URL: <http://devel.rtems.org/ticket/2870#comment:3>
RTEMS Project <http://www.rtems.org/>
RTEMS Project

More information about the bugs mailing list