On Sat, 24 Sep 2016, Sebastian Harl wrote:
> Is this still happening? I believe there were a few fixes that could be
> related to this in the past years. If it's still happening, we'll have
> to look into more details.
I wouldn't know if the bug still exists: I have stopped using collectd a
long
severity 600433 normal
thanks
On Sun, Oct 17, 2010 at 11:02:11AM -0200, Henrique de Moraes Holschuh wrote:
> On Sun, 17 Oct 2010, Florian Forster wrote:
> > On Sun, Oct 17, 2010 at 03:32:36AM -0200, Henrique de Moraes Holschuh wrote:
> > > collectd[2139]: uc_update: Value too old:name =
> > >
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
retitle 600433 collectd: rrd: issuing uc_update: Value too old messages
thanks
On Sun, 17 Oct 2010, Florian Forster wrote:
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
Package: collectd
Version: 4.10.1-1+squeeze1
Severity: important
Tags: upstream
Those who do not learn from the past, are bound to repeat the same
errors forever. collectd does not use UTC. Yet, it expects to be able
to ignore timezone shifts that happen twice an year on a very very large
5 matches
Mail list logo
