From: Roger Pack Date: 2010-01-29T02:33:24+09:00 Subject: [ruby-core:27936] Re: [Bug #2564] [patch] re-initialize timer_thread_{lock,cond} after fork > You should merge r25629 to 1.9.1. My patch is not necessary. And it doesn't solve issue completely as I see now. 'cause child can see some bad state left by running timer_thread_function. Maybe create a new ticket? > BTW, you can simplify rb_thread_create_timer_thread. There's no need to hold lock around pthread_create and there's no need to signal timer thread condition there. timer thread observes system_working in a reliable way, so there's no race with immediate native_stop_timer_thread and there's no gain in that for rb_thread_create_timer_thread. Patches are helpful :) -r