96ae89c801
Originally this was indended as a fix for devices without RTC support which do not have the correct time set after a reboot (until ntp is able to update the system time). vnstat checks if there is a time difference between the latest entry in the database and detects that the system time is incorrect. In this case vnstat does not start (to prevent database corruption), the following message is reported instead: 'Error: Interface "..." has previous update date too much in the future, exiting.' Once we have network connectivity (and ntp has updated the system time) vnstat starts correctly though. vnstat 1.18 fixes this by waiting a few minutes (instead of exiting) and the following message is logged: "Latest database update is in the future (db: 2018-04-28 08:39:11 > now: 2018-04-28 08:07:18). Giving the system clock up to 5 minutes to sync before continuing." This still adds a procd respawn trigger to let procd automatically restart vnstat in case: - vnstat it crashes - no valid system time is received for a long time (no network connectivity, broken NTP servers, ...) Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> |
||
|---|---|---|
| .. | ||
| vnstat.config | ||
| vnstat.defaults | ||
| vnstat.init | ||