#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 sebastian.huber):
Replying to [comment:3 joel.sherrill]:
> Replying to [comment:2 sebastian.huber]:
> > 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.
It seems the SNTP client of NTP Classic uses the libevent too
[https://svnweb.freebsd.org/base/head/contrib/ntp/sntp/libevent/].
--
Ticket URL: <http://devel.rtems.org/ticket/2870#comment:6>
RTEMS Project <http://www.rtems.org/>
RTEMS Project
_______________________________________________
bugs mailing list
[email protected]
http://lists.rtems.org/mailman/listinfo/bugs
