Cheshire Cat Computing

Hi Steve,

I think I have found another minor bug:
If the daystart/dayend variables are set, the marked area in the graphs is NOT relative to the timezone of the target but constant to the values set in the routers2.conf.

I have this one set:
---------------------------------------
# These hours may NOT cross midnight (ie, end > start) and are relative to the
# timezone of the target in question, or local timezone if not known.
daystart = 8
dayend = 18
---------------------------------------
But now I have one Target with the "Timezone[...]: Finland" directive and now the working day area is from 7 to 17 since finland is one hour ahead.

Ciao, Gerch

This may be down to the Time::Zone package not being installed on your system, and routers2 not being able to deduce the required hours offset from the timezone name (though the RRDs module, using compiled C libraries, can do it). We are using the timezone here in New Zealand (offset +12) without problem.

I will investigate this and see if I can verify

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11

Routers2 uses the Time::Zone package if it is installed to deduce the actual hour offset to use for the working day when given a timezone name. Of course, this requires that (a) Time::Zone be installed, and (b) the supplied timezone name is recognisable to it. Unfortunately, the timezone library used by MRTG may understand 'Auckland' but Time::Zone needs 'NZST' so there can be inconsistencies.

DateTime::TimeZone dones a similar thing, but Routers2 is only looking for Time::Zone. Probably it should look for both and use whichever it can find, but that's for a later version...

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11