Mailinglist Archive: opensuse-bugs (3112 mails)

< Previous Next >
[Bug 702217] syslog-ng stats_freq option not interpreted correctly

Balázs Scheidler <bazsi@xxxxxxxxxx> changed:

What |Removed |Added
CC| |bazsi@xxxxxxxxxx

--- Comment #2 from Balázs Scheidler <bazsi@xxxxxxxxxx> 2011-07-01 14:44:53 UTC
Hmm... I couldn't reproduce it with the latest syslog-ng 3.2 git tree, however
I can't remember any fixes in the area.

Are you sure you wrote the correct number of digits in the error report? I mean
one week is 24*60*60*7 = 604800 and not 60480 (one digit less).

This number is multiplied by 1000 to get msec instead of seconds, but that
gits into the 32 bit integer it is stored in. (around 600 million, but we're ok
until about 2 billion). The glib version can matter too, in my build
I use 2.14.6, yours is probably newer. This might also be a factor. (for
instance if glib uses nanoseconds internally, that would already overflow)

But anyway, I'd suggest to use shorter timeouts, is one per day so much extra
traffic? This way you can check message drops etc

So I wouldn't want to fix this upstream, especially as syslog-ng 3.3 is using
a completely different event library (ivykis instead of glib).

Configure bugmail:
------- You are receiving this mail because: -------
You are on the CC list for the bug.
< Previous Next >