now() -> now_to_tz
Fri Feb 28 11:51:17 CET 2003
On Fri, 28 Feb 2003, Per Hedeland wrote:
>Ulf Wiger <> wrote:
>> The rest of the system is always set for UTC. It's
>>worked for us so far.
>I'd think that would be a bit confusing, e.g. if you ever
>need to correlate Erlang-produced logs and system-produced
I was careful not to describe it as a perfect solution. (:
I agree that it can be confusing. The rule we try to enforce
is that all internal reporting should be done in UTC time.
Presentation to operators can be done in Local time. Thus,
the majority of the code should not care what timezone its
running in, and always use UTC.
In any event, reading logs where local time is used can be
quite confusing around the time of DST change. If UTC is
used, at least you get continuity in the log.
Ulf Wiger, Senior Specialist,
/ / / Architecture & Design of Carrier-Class Software
/ / / Strategic Product & System Management
/ / / Ericsson AB, Connectivity and Control Nodes
More information about the erlang-questions