Subj : Re: signaling threads from a forked child?
To   : comp.programming.threads
From : David Schwartz
Date : Tue Aug 09 2005 10:36 am


<markh@compro.net> wrote in message 
news:1123590986.791966.314480@f14g2000cwb.googlegroups.com...

> So are you saying that the setpshared/getpshared funtions are actually
> doing something? What code actually checks the PTHREAD_PROCESS_SHARED
> attr other than the getpshared funtion?  The kernel "currently"
> doesn't as far as I can see. Are these calls "as of the current" NTPL
> just fillers for code portability?  Are they so applications can check
> the PTHREAD_PROCESS_SHARED attr and willingly refuse to use the
> mutex/condv if not shared. I'm curious because I would like to safely
> run this app on LinuxThreads/2.4.x kernels and NPTL/2.6.x kernels???

    The functions exist in case something special needs to be done to make a 
mutex or condition variable process shared. If nothing special needs to be 
done, then they don't have to do anything.

    DS

.