PubTeX output 1998.09.24:1021

attributes(5)
Headers, Tables, and Macros
times umask uname
unlink utime wait
waitpid
write
MT-Safe with Exceptions
See the NOTES sections of these pages for a description of the exceptions.
Safe with Exceptions
See the NOTES sections of these pages for a description of the exceptions.
Fork1-Safe
A Fork1-Safe library releases the locks it had held whenever fork1(2) is
called in a Solaris thread program, or fork(2) in a POSIX (see
standards(5) )thread program. Calling fork(2) in a POSIX thread
program has the same semantic as calling fork1(2) in a Solaris thread
program. All system calls, libpthread , and libthread are Fork1-Safe
. Otherwise, you should handle the locking clean-up yourself (see
pthread_atfork(3T) ).
Cancel-Safety
If a multi-threaded application uses pthread_cancel(3T) to cancel (that
is, kill) a thread, it is possible that the target thread is killed while holding a
resource, such as a lock or allocated memory. If the thread has not installed
the appropriate cancellation cleanup handlers to release the resources
appropriately (see pthread_cancel(3T) ), the application is
"cancel-unsafe", that is, it is not safe with respect to cancellation. This
unsafety could result in deadlocks due to locks not released by a thread that
gets cancelled, or resource leaks; for example, memory not being freed on
thread cancellation. All applications that use pthread_cancel(3T) should
ensure that they operate in a Cancel-Safe environment. Libraries that have
cancellation points and which acquire resources such as locks or allocate
memory dynamically, also contribute to the cancel-unsafety of applications
that are linked with these libraries. This introduces another level of safety
for libraries in a multi-threaded program: Cancel-Safety. There are two
sub-categories of Cancel-Safety: Deferred-Cancel-Safety, and
Asynchronous-Cancel-Safety. An application is considered to be
Deferred-Cancel-Safe when it is Cancel-Safe for threads whose cancellation
type is PTHREAD_CANCEL_DEFERRED . An application is considered to be
Asynchronous-Cancel-Safe when it is Cancel-Safe for threads whose
19 SunOS 5.7 Last modified 3 June 1997