summaryrefslogtreecommitdiff
path: root/open_issues/alarm_setitimer.mdwn
diff options
context:
space:
mode:
authorPino Toscano <toscano.pino@tiscali.it>2012-06-19 00:53:40 +0200
committerPino Toscano <toscano.pino@tiscali.it>2012-06-19 00:53:40 +0200
commit59344d6c9615e22ecad1e9860b7e287bd92ea6fa (patch)
treeed010f39c7d5c2cc1f7f93b4c2dadfea3debd53b /open_issues/alarm_setitimer.mdwn
parent17f42781111a3c07f57718f79dd1ce098038ecbb (diff)
open_issues/alarm_setitimer: New.
Diffstat (limited to 'open_issues/alarm_setitimer.mdwn')
-rw-r--r--open_issues/alarm_setitimer.mdwn23
1 files changed, 23 insertions, 0 deletions
diff --git a/open_issues/alarm_setitimer.mdwn b/open_issues/alarm_setitimer.mdwn
new file mode 100644
index 00000000..99b2d7b6
--- /dev/null
+++ b/open_issues/alarm_setitimer.mdwn
@@ -0,0 +1,23 @@
+[[!meta copyright="Copyright © 2012 Free Software Foundation, Inc."]]
+
+[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
+id="license" text="Permission is granted to copy, distribute and/or modify this
+document under the terms of the GNU Free Documentation License, Version 1.2 or
+any later version published by the Free Software Foundation; with no Invariant
+Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license
+is included in the section entitled [[GNU Free Documentation
+License|/fdl]]."]]"""]]
+
+[[!meta title="alarm/setitimer"]]
+
+[[!tag open_issue_glibc open_issue_hurd]]
+
+`setitimer()`, called by `alarm()` when setting a new alarm, it is not able
+to disable on its own the timer when the alarm is fired the first time.
+On the other hand, manually invoking `alarm(0)` can cancel the running timer
+for `SIGALRM`.
+
+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]]