summaryrefslogtreecommitdiff
path: root/open_issues/alarm_setitimer.mdwn
diff options
context:
space:
mode:
authorThomas Schwinge <thomas@codesourcery.com>2012-08-07 23:25:46 +0200
committerThomas Schwinge <thomas@codesourcery.com>2012-08-07 23:25:46 +0200
commit7c23e08a4294373332b473d25173e4187ede0d5a (patch)
treefc6b35f1a03e127b2ca663edfd432dd0ac06d469 /open_issues/alarm_setitimer.mdwn
parentc5a84cd2d1ac772e2fe187201a36cd9cccf3951c (diff)
parent2603401fa1f899a8ff60ec6a134d5bd511073a9d (diff)
Merge remote-tracking branch 'fp/master'
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 ..)