Sponsored Content
Operating Systems Solaris Async-Signal-Safe versus MT-Safe Post 302304574 by tristan12 on Monday 6th of April 2009 08:16:05 PM
Old 04-06-2009
Async-Signal-Safe versus MT-Safe

Hi,

I am Solaris 9 developer and notice that the documentation does not provide a clear notion of the inherent concurrency in routines defined as "Async-Signal-Safe".

Routines defined as "MT-Safe" obviously have the best level of concurrency, compared to normal "Safe" interfaces.

I have noticed that the Solaris 10 documentation made an addition to attributes(5) that "Async-Signal-Safe" routines can also be assumed to be "MT-Safe".

My question is, can I make an assumption that Solaris 9 "Async-Signal-Safe" routines are also "MT-Safe"?

Thanks
 

We Also Found This Discussion For You

1. Shell Programming and Scripting

safe mode

Hello I'm working on a PHP project right now and when I try to run 'mkdir' I've been getting an error: code: mkdir("<full path>/test", 0700); error: PHP Warning: mkdir() : SAFE MODE Restriction in effect. The script whose uid is 10002 is not allowed to access <full path> owned by uid... (2 Replies)
Discussion started by: recluse8912
2 Replies
rpc_gss_mech_to_oid(3N) 												   rpc_gss_mech_to_oid(3N)

NAME
rpc_gss_mech_to_oid(), rpc_gss_qop_to_num() - map mechanism, QOP strings to non-string values SYNOPSIS
DESCRIPTION
Because in-kernel RPC routines use non-string values for mechanism and Quality of Protection (QOP), these routines exist to map strings for these attributes to their non-string counterparts. (The non-string values for QOP and mechanism are also found in the and files, respec- tively.) takes a string representing a mechanism, as well as a pointer to a object identifier structure. It then gives this structure values corresponding to the indicated mechanism, so that the application can now use the OID directly with RPC routines. does much the same thing, taking strings for QOP and mechanism and returning a number. PARAMETERS
Information on data types for parameters may be found on the rpcsec_gss(3N) manpage. mech An ASCII string representing the security mechanism in use. Valid strings may be found in the file. oid An object identifier of type whose elements are usable by kernel-level RPC routines. qop This is an ASCII string which sets the quality of protection (QOP) for the session. Appropriate values for this string may be found in the file num The non-string value for the QOP. MULTITHREAD USAGE
Thread Safe: Yes Cancel Safe: Yes Fork Safe: No Async-cancel Safe: No Async-signal Safe: No These functions can be called safely in a multithreaded environment. They may be cancellation points in that they call functions that are cancel points. In a multithreaded environment, these functions are not safe to be called by a child process after and before These functions should not be called by a multithreaded application that supports asynchronous cancellation or asynchronous signals. RETURN VALUE
Both functions return if they are successful, otherwise. FILES
File containing valid security mechanisms. File containing valid QOP values. SEE ALSO
rpc(3N), rpc_gss_get_error(3N), rpc_gss_get_mechanisms(3N), rpcsec_gss(3N), mech(4), qop(4). rpc_gss_mech_to_oid(3N)
All times are GMT -4. The time now is 03:51 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy