Hi On Sat, Sep 13, 2014 at 6:54 PM, Marcel Holtmann <marcel@xxxxxxxxxxxx> wrote: > while setting WatchdogSec=1 is pretty insane interval anyway, this now also means that setting it that low will cause a race condition between systemd's watchdog killing us and we are able to be quickly enough to respond with a keep alive message. Whoops, indeed. The patch is stupid. And yes, WatchdogSec=1 is insane, but I guess we should at least have a sane behavior. I mean, it's user-config so someone will (and currently is!) trigger this. > I get the feeling that if > 2s, then we should use g_timeout_add_seconds to get the advantage of being woken up with all other timeouts in our daemon. And when it is <= 2s, then we better use a high precision g_timeout_add. This sounds actually good. I will do that in v2. Thanks David > One alternative is to actually use timerfd natively here and use kernel based range timers. > > Regards > > Marcel > -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
