From 95022ca95b1d2792bae447d90694dcc0d67b9de2 Mon Sep 17 00:00:00 2001 From: fusion32 Date: Thu, 16 Oct 2025 01:35:10 -0300 Subject: lower monotonic uptime resolution from MILLISECONDS to SECONDS The monotonic uptime was used exclusively with caches and having a resolution of SECONDS allows it to be stored as an int without risk of wrapping (~68 years). Using MILLISECONDS meant that it would wrap after ~25 days which is totally possible and EXPECTED. Just as an example, the small test server I ran for about 1 month had ZERO downtime on the QueryManager except for when I manually restarted it. It was probably very close to wrapping when I took it down. --- src/querymanager.hh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/querymanager.hh') diff --git a/src/querymanager.hh b/src/querymanager.hh index 46ea80d..220f69a 100644 --- a/src/querymanager.hh +++ b/src/querymanager.hh @@ -148,7 +148,7 @@ void LogAddVerbose(const char *Prefix, const char *Function, struct tm GetLocalTime(time_t t); struct tm GetGMTime(time_t t); int64 GetClockMonotonicMS(void); -int GetMonotonicUptimeMS(void); +int GetMonotonicUptime(void); void SleepMS(int DurationMS); void CryptoRandom(uint8 *Buffer, int Count); int RoundSecondsToDays(int Seconds); -- cgit v1.2.3