summaryrefslogtreecommitdiffstats
path: root/lib/libc/gen/usleep.c
Commit message (Collapse)AuthorAgeFilesLines
* Fix known issues which blow up the process after dlopen("libthr.so")kib2015-01-181-1/+4
| | | | | | | | | | | | | | | | | | | | | (or loading a dso linked to libthr.so into process which was not linked against threading library). MFC r276630: Remove interposing, fix malloc, reinstall signal handlers wrappers on libthr load. MFC r276681: Avoid calling internal libc function through PLT or accessing data though GOT. MFC r277032: Reduce the size of the interposing table and amount of cancellation-handling code in the libthr. MFC note: r276646 ("do not erronously export 'openat' symbol from rtld") is not applicable to stable/10 yet, since PATHFDS support was not merged.
* Fix many "function declaration isn't a prototype" warnings in libc.ed2009-12-051-2/+1
| | | | | I've only fixed code that seems to be written by `us'. There are still many warnings like this present in resolv/, rpc/, stdtime/ and yp/.
* Per Regents of the University of Calfornia letter, remove advertisingimp2007-01-091-4/+0
| | | | | | clause. # If I've done so improperly on a file, please let me know.
* Make usleep() overridable by the thread libraries so they can providedeischen2005-08-031-1/+4
| | | | | | cancellation points. Noticed by: phk
* Use `useconds_t' instead of `u_int' or `unsigned int' where appropriate.mike2002-12-291-1/+1
|
* Fix SCM ID's.obrien2002-02-011-4/+2
|
* Remove _THREAD_SAFE and make libc thread-safe by default bydeischen2001-01-241-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | adding (weak definitions to) stubs for some of the pthread functions. If the threads library is linked in, the real pthread functions will pulled in. Use the following convention for system calls wrapped by the threads library: __sys_foo - actual system call _foo - weak definition to __sys_foo foo - weak definition to __sys_foo Change all libc uses of system calls wrapped by the threads library from foo to _foo. In order to define the prototypes for _foo(), we introduce namespace.h and un-namespace.h (suggested by bde). All files that need to reference these system calls, should include namespace.h before any standard includes, then include un-namespace.h after the standard includes and before any local includes. <db.h> is an exception and shouldn't be included in between namespace.h and un-namespace.h namespace.h will define foo to _foo, and un-namespace.h will undefine foo. Try to eliminate some of the recursive calls to MT-safe functions in libc/stdio in preparation for adding a mutex to FILE. We have recursive mutexes, but would like to avoid using them if possible. Remove uneeded includes of <errno.h> from a few files. Add $FreeBSD$ to a few files in order to pass commitprep. Approved by: -arch
* Simplify sytem call renaming. Instead of _foo() <-- _libc_foo <-- foo(),jasone2000-01-271-1/+1
| | | | | | | | | | | | | | | | | just use _foo() <-- foo(). In the case of a libpthread that doesn't do call conversion (such as linuxthreads and our upcoming libpthread), this is adequate. In the case of libc_r, we still need three names, which are now _thread_sys_foo() <-- _foo() <-- foo(). Convert all internal libc usage of: aio_suspend(), close(), fsync(), msync(), nanosleep(), open(), fcntl(), read(), and write() to _foo() instead of foo(). Remove all internal libc usage of: creat(), pause(), sleep(), system(), tcdrain(), wait(), and waitpid(). Make thread cancellation fully POSIX-compliant. Suggested by: deischen
* Add three-tier symbol naming in support of POSIX thread cancellationjasone2000-01-121-1/+1
| | | | | | points. For library functions, the pattern is __sleep() <-- _libc_sleep() <-- sleep(). The arrows represent weak aliases. For system calls, the pattern is _read() <-- _libc_read() <-- read().
* $Id$ -> $FreeBSD$peter1999-08-281-1/+1
|
* Don't check for the unlikely case of useconds == 0 here. The kernelbde1997-11-201-7/+4
| | | | | | checks it. Fixed a style bug.
* Back out part of OpenGroup specs about limiting max arg since it may breakache1997-10-221-8/+3
| | | | compatibility.
* Changes in spirit of OpenGroup Singe Unix specs:ache1997-10-221-5/+11
| | | | | | 1) Limit max allowed argument to 1000000 2) Change return type from void to int to indicate premature termination (by signal)
* Add $Idache1997-10-171-0/+4
|
* Cleanup #includesache1997-10-161-3/+1
|
* Remove old SIGALRM absorbing back-compat code. It wasn't working at allpeter1997-10-151-83/+1
| | | | | | | | | | | | | for the entire time that it was there, so obviously nothing needs it anymore. Note, unix98/single-unix spec v2 says that usleep() returns an int rather than a void, to indicate whether the entire time period elapsed (0) or an error (eg: signal handler) interrupted it (returns -1, errno = EINTR) It is probably useful to make this change but I'll test it locally first to see if this will break userland programs [much]... Reviewed by: ache, bde
* Oops, fix logic for previous commitache1997-08-141-5/+5
|
* Break loop if error != EINTR occurse or it can take forever withache1997-08-141-2/+5
| | | | time_remaining unchanged
* Handle syscalls error return slightly betterache1997-08-131-6/+12
|
* Back out my installation of SIGALRM handler even if it is blockedache1997-08-121-19/+29
| | | | | | | and return to previous Peter's variant. POSIX says that this place is implementation defined and old variant allows application block SIGALRM and sleep and not be killed by external SIGALRMs. BTW, GNU sleep f.e. sleeps forever in blocked SIGALRM :-)
* 1) Make usleep() terminateable by alarm (or ualarm) as supposedache1997-08-121-4/+8
| | | | | historically 2) Fix end of time loop condition: && -> ||
* Make sleep() and usleep() "eat" any stray SIGALRM signals during thepeter1997-07-181-24/+14
| | | | | | | | lifetime of the call, just like the old implementation did. Previously, we were only eating them if the application did not call sleep()/usleep() with SIGALRM masked. Submitted by: ache
* Re-activate the nanosleep style using code, but with the signal handlingpeter1997-06-021-57/+1
| | | | | | | | | | semantics of the old sleep for compatability with a few decades of expected side effects. Apache breaks if we just use nanosleep() for some reason, here we use a new signanosleep() syscall which is kinda like a hybrid of sigsuspend and nanosleep.. Reviewed by: ache (and tested on his apache that was failing when sleep used plain nanosleep)
* Update the sleep(3)/usleep(3) code to use signanosleep(2) if compiled withpeter1997-06-011-8/+58
| | | | | | | -DUSE_NANOSLEEP. Also, seperate the code for _THREAD_SAFE so that it uses the simpler threaded nanosleep() call in libc_r.. We don't go to the same extremes for emulating traditional sleep semantics (ie: eating any SIGALRM that might happen) which things like apache seem to depend on.
* Update the nanosleep versions to set a SIGALRM handler while sleeping.peter1997-05-181-1/+9
| | | | | This appears to appease Apache, although depending on having sleep(3) changing the SIGALRM handler is a bit bogus.
* if nanosleep returns too early, loop. usleep() does not have a returnpeter1997-05-171-2/+7
| | | | | | value, it appears as though the semantics of usleep are that it doesn't return early. (only in the nanosleep code - the setitimer code does this already)
* Allow conditional use (add -DUSE_NANOSLEEP) to CFLAGS of nanosleep() forpeter1997-05-171-15/+15
| | | | | the backend of sleep(3) and usleep(3). It's off by default until the problem is fixed.
* Fix typo from previous commit (tsvsec --> tv_sec).alex1996-09-231-1/+1
|
* ts_sec -> tv_secnate1996-09-201-2/+2
| | | | ts_nsec -> tv_nsec
* Reviewed by: julian and (hsu?)julian1996-01-221-1/+18
| | | | | | Submitted by: John Birrel(L?) changes for threadsafe operations
* Minor cleanup, mostly unused vars and missing #includes.phk1995-10-221-1/+1
|
* BSD 4.4 Lite Lib Sourcesrgrimes1994-05-271-0/+99
OpenPOWER on IntegriCloud