summaryrefslogtreecommitdiff
path: root/open_issues/alarm_setitimer.mdwn
diff options
context:
space:
mode:
authorThomas Schwinge <thomas@codesourcery.com>2012-12-11 11:04:11 +0100
committerThomas Schwinge <thomas@codesourcery.com>2012-12-11 11:04:11 +0100
commit1c36eb6c025084af76c5b930ca4adc5953560fd7 (patch)
tree8ac3bcf1f785997cce064c65dcd729be4c5dcb0b /open_issues/alarm_setitimer.mdwn
parenta0290d994030cd14bdccbb97d2a2c022d1d2428c (diff)
parentbcfc058a332da0a2bd2e09e13619be3e2eb803a7 (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 ..)