> One thing that has always bothered me with the NTP project, is the lack of a separate daemon and client.
> In most cases, such as on my laptop, workstations, and embedded systems, I don't want the complexities of a full blown daemon running
Pretty confused. Why would you care about a code path that isn't executed? Are upset about losing a few kb of disk space? What is the alternative to "a full blown daemon". Can you demonstrate how that is an issue for anyone?
Your comment also shows a fundamental misunderstanding of NTP. It's a peer-to-peer protocol in many use cases, as is PTP so instances have to run as client & server.
> In most cases, such as on my laptop, workstations, and embedded systems, I don't want the complexities of a full blown daemon running
Pretty confused. Why would you care about a code path that isn't executed? Are upset about losing a few kb of disk space? What is the alternative to "a full blown daemon". Can you demonstrate how that is an issue for anyone?
Your comment also shows a fundamental misunderstanding of NTP. It's a peer-to-peer protocol in many use cases, as is PTP so instances have to run as client & server.