1·Fear not, you'll still have access to the raw mongrel request if you want to do fancy stuff like streaming or deferred rendering outside the mutex.
不用害怕，如果您想在互斥以外做一些奇特的事情，比如流处理或延迟呈现，您仍然可以访问原始的 mongrel 请求。
2·The error is not due to the locked mutex.
那个错误不是归咎于被锁定的互斥。
3·Mutexes have names, and only one mutex of a given name can exist on a machine at a time.
互斥有名称，并且，一个给定名称的互斥在同一机器上同一时刻只能存在一个。
4·This function gets a pointer to the mutex it is trying to lock.
这个函数会获得一个指向它正在尝试锁定的互斥的指针。
5·However, a mutex should accompany each condition variable.
不过，每个条件变量都应该伴有一个互斥。
1·Once you have it, no one can take it away from you until you put it down. The process of picking up the unique object is called locking, or acquiring, the mutex.
占有这个惟一物体的过程就叫做锁定或者获得互斥量。
2·The function primarily used for this is pthread_cond_wait . It takes two arguments; the first is a pointer to a condition variable, and the second is a locked mutex.
函数pthread_cond_wait主要就是用于阻塞线程的，它有两个参数；第一个是一个指向条件变量的指针，第二个是一个锁定了的互斥量。
3·When invoked, pthread_cond_wait unlocks the mutex and then pauses execution of its thread.
当pthread_cond_wait被调用后，它解锁互斥量并停止线程的执行。
4·Main thread: Lock mutex and increment threadcount.
主线程：锁定互斥量并增量threadcount。
5·Finally, the first thing any thread tries to do when waking up from pthread_cond_wait is re-lock the mutex it unlocked when initially called.
最后，当一个线程从调用pthread_cond_wait而被唤醒时，要做的第一件事就是重新锁定它在最初调用时解锁的那个互斥量。
1·Meanwhile, another handle you forced closed was reused as a mutex handle, which is used to help prevent data from being corrupted.
同时，另一个句柄您强制关闭时重用作为用于帮助防止数据被损坏一个互斥体句柄。
2·I know it has something to do with some mythical thing called a mutex, rarely can I find someone that bothers to stop and explain what one of these are.
我知道它是与一些神秘的东西叫一个互斥体，很少我可以找人困扰停下来解释其中之一是。
3·Open an existing named mutex, specifying the desired security access.
打开现有的已命名互斥体，并指定所需的安全访问权。