https://github.com/piotrmaslanka/chronia

[DEPRECATED, use fake-hwclock instead] What if your RTC-less device has no Internet?
https://github.com/piotrmaslanka/chronia

Last synced: 7 days ago
JSON representation

[DEPRECATED, use fake-hwclock instead] What if your RTC-less device has no Internet?

• Host: GitHub
• URL: https://github.com/piotrmaslanka/chronia
• Owner: piotrmaslanka
• License: bsd-3-clause
• Created: 2015-08-30T11:39:15.000Z (about 9 years ago)
• Default Branch: master
• Last Pushed: 2015-08-30T12:48:54.000Z (about 9 years ago)
• Last Synced: 2023-03-12T09:41:51.931Z (over 1 year ago)
• Language: Python
• Homepage:
• Size: 137 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: COPYING

Awesome Lists containing this project

README

        
chronia

=======

You have a device that doesn't have RTC? That sucks.

The device sometimes won't have Internet access, and it can reboot, so you will be lost without time? That sucks even more.

What if your no-RTC device can't get on the Internet?

-----------------------------------------------------

Sometimes your no-RTC device will happen to reboot. Then, it will find out the hard way it has no Internet and no capability

to get current time.

Chronia was thought as a NTP supplement service for Raspberry Pi in situations that Pi would spontaneously reboot and, upon

awakening, discover it was cut off from WAN. Chronia will sync time each interval (default a minute) with the filesystem,

so that when it wakes up and fails to roll NTP, it will get time from there (correcting for uptime).

When WAN recovers, your system NTP client will synchronize the time properly. Chronia will notice this, and keep trailing

the proper time.

tl;dr - use Chronia when you think that time possibly late by some period is better than no time at all.

Recipe

------

Just run chronia alongside your NTP client. They will get together nicely.