search

twekkel / htpdate

HTTP Time protocol
https://www.vervest.org/htp
Other
50 stars 13 forks source link

Feed daemon updates into Chrony #26

Closed hongkongkiwi closed 2 years ago

hongkongkiwi commented 2 years ago

I love the idea of HTPDate, it's perfect for firewalled environments.

For devices which will be moving between firewalled and not, it would be great if htpdate could play nice with Chrony.

Using Chrony SOCK protocol we could feed updates to Chrony, so that HTPDate daemon could become another chrony timesource for if/when NTP is blocked or not available due to firewall.

Any chance this feature could be considered?

Chrony uses SOCK protocol to handle incoming updates (basically

hongkongkiwi commented 2 years ago

It sounds complicated, but I believe the format is pretty simple, Chrony creates the SOCK file, then you just have to check if the sock file exists and then send data in a specific format, here's an example from GPSD: https://github.com/traveller42/gpsd/blob/774f18e9e27a5934fd0e3e514ea47de88ca9b5ba/timehint.c#L309

twekkel commented 2 years ago

I'm not considering this option. You can just run both daemons at the same time. Feel free to fork and implement!

On Aug 13, 2022, 08:57, at 08:57, Andy @.***> wrote:

I love the idea of HTPDate, it's perfect for firewalled environments.

For devices which will be moving between firewalled and not, it would be great if htpdate could play nice with Chrony.

Using Chrony SOCK protocol we could feed updates to Chrony, so that HTPDate daemon could become another chrony timesource for if/when NTP is blocked or not available due to firewall.

Any chance this feature could be considered?

Chrony uses SOCK protocol to handle incoming updates (basically

-- Reply to this email directly or view it on GitHub: https://github.com/twekkel/htpdate/issues/26 You are receiving this because you are subscribed to this thread.

Message ID: @.***>