Bug#606618: glib2.0: g_timeout_add() cannot handle very large timeouts

[Emilio Pozuelo Monfort]

On 11/12/10 17:52, Jakub Wilk wrote:
> * Jakub Wilk <jwilk at debian.org>, 2010-12-10, 13:36:
>> I have "stats_freq(86400)" in my syslog-ng.conf, and it used to work fine
>> until I upgraded libglib2.0-0 from 2.24.2-1 to 2.27.4-1. Apparently statistics
>> are now logged every 8m30s (rather than every 24h, as I requested).
> 
> I turns out this is a bug in glib. The attached minimal test program should go
> ping every ~24 hours, and it apparently does with glib 2.24.2-1, but not with
> 2.27.4-1:

Any reason you don't use g_timeout_add_seconds for large timeouts? that will
cause less wakeups (so less power consumption) and I guess precision is not a
concern for such timeouts...

Cheers,
Emilio