41b
Subj : Re: signaling threads from a forked child?
To   : comp.programming.threads
From : Joe Seigh
Date : Tue Aug 09 2005 10:13 am

markh@compro.net wrote:
> 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???
> 
Behavior that is specified as undefined cannot be relied upon.  If you
don't set the process shared attribute there is no guarantee that your
code will work on other platforms or on other releases.


-- 
Joe Seigh

When you get lemons, you make lemonade.
When you get hardware, you make software.

.

0