if it is UNIX time then it won't be a problem.
If local time is stored then used to calculate, it'd be a problem. If it is
only for display or history, it'd probably be ok.
Possible problem scenarios
- duration for alerts could be wrong, if the event timestamp was
recorded in local time.
- ignore for a given number of hours when acknowledging an event, if
the acknowledgment timestamp was stored in local time.
On 3/6/07, Henrik Stoerner <user-ce4a2c883f75@xymon.invalid> wrote:
On Tue, Mar 06, 2007 at 11:29:35AM -0500, Jerry Yu wrote:
I didn't find any question asked about 2007 DST readiness for Hobbit on
the
list. Should it be assumed it won't be problem at all? For one thing,
the
scheduled downtime and such would be specific to local time. Assume the
underlying operating system has been patched and is ready to accommodate
2007
DST changes in North America.
All time recorded in Hobbit uses either the Unix timestamp - which is
unaffected by DST changes - or the local time of some event which has
occurred (for history logging).
So I cannot see that there should be any problems, assuming your OS has
been updated to handle the new DST changes (usually, an update to your
timezone definition files).
Regards,
Henrik