aboutsummaryrefslogtreecommitdiff
path: root/open_issues/alarm_setitimer.mdwn
diff options
context:
space:
mode:
authorThomas Schwinge <tschwinge@gnu.org>2012-08-07 23:25:26 +0200
committerThomas Schwinge <tschwinge@gnu.org>2012-08-07 23:25:26 +0200
commit2603401fa1f899a8ff60ec6a134d5bd511073a9d (patch)
treeccac6e11638ddeee8da94055b53f4fdfde73aa5c /open_issues/alarm_setitimer.mdwn
parentd72694b33a81919368365da2c35d5b4a264648e0 (diff)
downloadweb-2603401fa1f899a8ff60ec6a134d5bd511073a9d.tar.gz
web-2603401fa1f899a8ff60ec6a134d5bd511073a9d.tar.bz2
web-2603401fa1f899a8ff60ec6a134d5bd511073a9d.zip
IRC.
Diffstat (limited to 'open_issues/alarm_setitimer.mdwn')
-rw-r--r--open_issues/alarm_setitimer.mdwn8
1 files changed, 8 insertions, 0 deletions
diff --git a/open_issues/alarm_setitimer.mdwn b/open_issues/alarm_setitimer.mdwn
index 99b2d7b6..3255683c 100644
--- a/open_issues/alarm_setitimer.mdwn
+++ b/open_issues/alarm_setitimer.mdwn
@@ -21,3 +21,11 @@ See also the attached file: on other OSes (e.g. Linux) it blocks waiting
for a signal, while on GNU/Hurd it gets a new alarm and exits.
[[alrm.c]]
+
+
+# IRC, freenode, #hurd, 2012-07-29
+
+ <braunr> our setitimer is bugged
+ <braunr> it seems doesn't seem to leave a timer disarmed when the interval
+ is set to 0
+ <braunr> (which means a one shot timer is actually periodic ..)