Hi Henrique, On Sun, Oct 17, 2010 at 03:32:36AM -0200, Henrique de Moraes Holschuh wrote: > collectd does not use UTC.
collectd uses the timestamp returned by time(3). To the best of my
knowledge, it returns the number of seconds since 00:00:00 January 1st,
1970 _UTC_ and should, as such, not be dependent on any timezone
setting.
> collectd[2139]: uc_update: Value too old:name = <REMOVED>/temperature-temp1;
> value time = 1287260393; last cache update = 1287260393;
If the timestamp was influenced by the timezone shift, "value time"
should be 1-3600 seconds smaller than "last cache update" [0]. The two
values are identical, though, which is 99.9% of all cases means that the
identifier ((file)name of the data) is not unique. Maybe the names
returned by lm_sensors are not unique or you're collecting the
temperature of the same HDD twice.. Either way, the timezone shift is
just coincidental.
Regards,
--octo
[0] If the time jumped forwards (== bigger) then there wouldn't be an
error message, just a gap in the data.
--
Florian octo Forster
Hacker in training
GnuPG: 0x0C705A15
http://octo.it/
signature.asc
Description: Digital signature
