secure_rpc.3n (2010 09)

s
secure_rpc(3N) secure_rpc(3N)
In a multithreaded environment, these functions are not safe to be called by a child process after
fork()
and before exec(). These functions should not be called by a multithreaded application that supports
asynchronous cancellation or asynchronous signals.
SEE ALSO
chkey(1), keyserv(1M), newkey(1M), rpc(3N), rpc_clnt_auth(3N).
4 Hewlett-Packard Company − 4 − HP-UX 11i Version 3: September 2010