summaryrefslogtreecommitdiff
path: root/open_issues/usleep.mdwn
blob: b71cd902152f1b441629b7f11593dcfa9e4f5710 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
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
License|/fdl]]."]]"""]]

[[!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.»