Did you look at the Time Warp flags in that post I linked about Erlang time? In particular this seems maybe applicable:
+C single_time_warpThis is a special hybrid mode to be used on embedded hardware when you know Erlang boots before the OS clock is synchronized. It works in two phases:
- a.(with
+c true) When the system boots, the monotonic clock is kept as stable as possible, but no system time adjustments are made
b. (with+c false) Same asno_time_warp- The user calls
erlang:system_flag(time_offset, finalize), the Erlang system time warps once to match the OS system time, and then the clocks become equivalent to those underno_time_warp.






















