Async-Signal-Safe versus MT-Safe


 
Thread Tools Search this Thread
Operating Systems Solaris Async-Signal-Safe versus MT-Safe
# 1  
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
# 2  
Old 04-07-2009
See this thread -
"No child processes" and waitpif

async-signal safe is going to be thread safe. The other way around: thread safe is async safe -- not always true.
Login or Register to Ask a Question

Previous Thread | Next Thread

1 More Discussions You Might Find Interesting

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
Login or Register to Ask a Question