USLEEP(3) BSD Library Functions Manual USLEEP(3)NAME
usleep -- suspend thread execution for an interval measured in microseconds
LIBRARY
Standard C Library (libc, -lc)
SYNOPSIS
#include <unistd.h>
int
usleep(useconds_t microseconds);
DESCRIPTION
The usleep() function suspends execution of the calling thread until either microseconds microseconds have elapsed or a signal is delivered
to the thread and its action is to invoke a signal-catching function or to terminate the process. System activity or limitations may
lengthen the sleep by an indeterminate amount.
This function is implemented using nanosleep(2) by pausing for microseconds microseconds or until a signal occurs. Consequently, in this
implementation, sleeping has no effect on the state of process timers, and there is no special handling for SIGALRM. Also, this implementa-
tion does not put a limit on the value of microseconds (other than that limited by the size of the useconds_t type); some other platforms
require it to be less than one million.
NOTE
The usleep() function is obsolescent. Use nanosleep(2) instead.
RETURN VALUES
The usleep() function returns the value 0 if successful; otherwise the value -1 is returned and the global variable errno is set to indicate
the error.
ERRORS
The usleep() function will fail if:
[EINTR] A signal was delivered to the process and its action was to invoke a signal-catching function.
SEE ALSO nanosleep(2), sleep(3)HISTORY
The usleep() function appeared in 4.3BSD.
BSD February 13, 1998 BSD
Check Out this Related Man Page
USLEEP(3) BSD Library Functions Manual USLEEP(3)NAME
usleep -- suspend execution for interval of microseconds
LIBRARY
Standard C Library (libc, -lc)
SYNOPSIS
#include <unistd.h>
int
usleep(useconds_t microseconds);
DESCRIPTION
The usleep() function suspends execution of the calling process until either the number of microseconds specified by microseconds have
elapsed or a signal is delivered to the calling process and its action is to invoke a signal catching function or to terminate the process.
The suspension time may be longer than requested due to the scheduling of other activity by the system.
The microseconds argument must be less than 1,000,000. If the value of microseconds is 0, then the call has no effect.
RETURN VALUES
On successful completion, usleep() returns 0. Otherwise, it returns -1 and sets errno to indicate the error.
ERRORS
The usleep() function may fail if:
[EINVAL] The microseconds interval specified 1,000,000 or more microseconds.
SEE ALSO nanosleep(2), sleep(3)STANDARDS
The usleep() function conforms to X/Open Portability Guide Issue 4, Version 2 (``XPG4.2''). It later appeared in the POSIX standard, but in
IEEE Std 1003.1-2004 (``POSIX.1'') it was marked as legacy and the use of nanosleep(2) was recommended instead. The IEEE Std 1003.1-2008
(``POSIX.1'') revision removed usleep() from the specification.
HISTORY
The usleep() function appeared in 4.3BSD.
BSD April 29, 2010 BSD
Hi,
I'm using the command usleep (500000) when compiling C++ on the SunOS platform, but it does not compile on a OSF1 platform?
Any ideas?
Thanks (5 Replies)
Hello,
Can anyone, please, guide me on the use of nanosleep. I'm learning threads. I want to introduce a delay (not nested for loops, something more customizable). Nanosleep looked useful (or any other form of customizable and easy-to-use delay). Sleep is too long. :) (2 Replies)
Hi,
I have encountered the following problem on Solaris 10:
I have a thread that is asleep on nanosleep (set to 24 hours).
Something that happens on another thread, causes the nanosleep to exit, even though the time has not elapsed.
The returned value is 0 (so it doesn't look like it... (1 Reply)
Hi All,
I need usleep command to use in one of my shell script. I am working on SunOS 5.9. Where usleep command is not available. Is there any way to use usleep command in SunOS.
Thanks In Advance,
chidhu (5 Replies)
Hi ,
How can I use floating point argument for sleep command in unix.I cannot use usleep as it is not suppported.
Also how can I find out that a file is in use at that particular instant only.(wether it is being read or written) (7 Replies)
Hi @ll :)
I have a problem with my code but first a short description:
1. I have one signal call SIGUSR1
2. In the signal I try to use nanosleep and now:
When I put kill -SIGUSR1 pid --> sometimes works fine, sometimes returns me an error with ,,Interrupt system call", sometimes I got... (5 Replies)