On Mon, 2013-11-25 at 23:52 +0100, Lennart Poettering wrote:
Of course, timer callbacks should only be called once, ence
ONESHOT mode is the default -- unless you change that explicitly.
If this doesn't solve the issue, I wouldn't be surprised if there was
still a bug lurking with the
On Mon, 09.12.13 23:41, Patrik Flykt (patrik.fl...@linux.intel.com) wrote:
On Mon, 2013-11-25 at 23:52 +0100, Lennart Poettering wrote:
Of course, timer callbacks should only be called once, ence
ONESHOT mode is the default -- unless you change that explicitly.
If this doesn't solve
Hi,
On Mon, 2013-11-25 at 23:52 +0100, Lennart Poettering wrote:
Of course, timer callbacks should only be called once, ence ONESHOT
mode is the default -- unless you change that explicitly.
Event loop code said ONESHOT for timers, and I don't think I managed to
change that.
If
On Mon, 25.11.13 09:13, Patrik Flykt (patrik.fl...@linux.intel.com) wrote:
After that I noticed someting interesting when setting a monotonic timer
event to go off at time 0. It seems to repeatedly call the timer event
without stopping, either due to the next timer computation going wrong in
Hi,
Here is version 2 of the libsystemd-dhcp patch set fixed according to
comments. Functionality is the same as in the earlier version. I'm still
usin src/dhcp as the location for this code, but what might be the proper
directory for the code eventually? I also left it conditionally
