path: root/open_issues/usleep.mdwn
diff options
authorThomas Schwinge <>2012-08-07 23:25:26 +0200
committerThomas Schwinge <>2012-08-07 23:25:26 +0200
commit2603401fa1f899a8ff60ec6a134d5bd511073a9d (patch)
treeccac6e11638ddeee8da94055b53f4fdfde73aa5c /open_issues/usleep.mdwn
parentd72694b33a81919368365da2c35d5b4a264648e0 (diff)
Diffstat (limited to 'open_issues/usleep.mdwn')
1 files changed, 25 insertions, 0 deletions
diff --git a/open_issues/usleep.mdwn b/open_issues/usleep.mdwn
new file mode 100644
index 00000000..b71cd902
--- /dev/null
+++ b/open_issues/usleep.mdwn
@@ -0,0 +1,25 @@
+[[!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
+[[!tag open_issue_glibc]]
+# IRC, OFTC, #debian-hurd, 2012-07-14
+ <pinotree> eeek, usleep has the issues which i fixed in nanosleep
+ <bdefreese> pinotree: ?
+ * pinotree ponders a `mv sysdeps/unix/sysv/linux/usleep.c
+ sysdeps/mach/usleep.c`
+ <pinotree> s/mv/cp/
+ <bdefreese> What the heck is the point of usleep(0) anyway? Isn't that
+ basically saying suspend for 0 milliseconds?
+ <youpi> it's rounded up by the kernel I guess
+ <youpi> i.e. suspend for the shortest time possible (a clock tick)
+ <pinotree> posix 2001 says that «If the value of useconds is 0, then the
+ call has no effect.»