On 05/20/2015 11:31 AM, Donald G Porter wrote:
>>> 2) The new routine should only be called when the mutex argument>>> is locked. How is it known in the AtForkChild() callback that>>> this is the case?
Looking at the proposed implementation of Tcl_MutexUnlockAndFinalize(),
it appears that it's also important when AtForkChild() runs that the
"master" lock is unlocked, and the "mutex lock serialization" lock
is also unlocked. How can these states be known when AtForkChild()
runs?
Sorry for all the dumb questions. Bright side is if you explain things
so I get it, it should be clear to all the other dummies out there too.
--
| Don Porter Applied and Computational Mathematics Division |
| dona...@nist.gov Information Technology Laboratory |
| http://math.nist.gov/~DPorter/ NIST |
|______________________________________________________________________|
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Tcl-Core mailing list
Tcl-...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tcl-core