nonlinearity of time

Press RESET immediately, All! The time in the logs is written in local time. When making a time change consistently 2 times a year it is impossible to correctly calculate the time elapsed between two entries in the log, and once per year it is impossible to determine at what specific point in time (absolute meaning, for example UTC) a log entry occurred (before or after the time was set back). What could be the ways to overcome the problem? I understand that if wrote programs In the log UTC time there would be no problem, but they write local. Now if only log entry was carried out through a special demon, which would set the time itself, or wrote down in the log a label indicating the translation of local time... but with strong system boot (just imagine everything froze for a couple of hours) it may still be entered incorrectly time (axis and programs do not work in real time). How about from a practical point of view? There are programs for which the accuracy time log entries is of fundamental importance (in terms of machine processing). Install TZ=UTC is possible, but undesirable. * Originally in RU.LINUX *Crossposted in ZXNET.PC