https://issues.apache.org/bugzilla/show_bug.cgi?id=55153
--- Comment #9 from Harald Oehlmann <[email protected]> --- TCL was modified, that Tcl_InitNotifier also starts the thread if we are forked. Using that, fileevents do fire. An alternate solution I see would to create the Tcl interpreter after the fork, which would vanish advantages by the general init script... Required modifications in Rivet are: mod_rivet.c : Put Tcl_InitNotifier(); somewhere at the beginning of function: Rivet_InitTclStuff Alternate test script is: --test_file_async.tcl-- set q I set h [open /usr/tmp/test.txt w] set idafter [after 100000 "set q T"] fileevent $h writable "set q W;after cancel [after 1000 "set q T"]" vwait q close $h puts $q file delete /usr/tmp/test.txt -EOF Here is the tcl RFE: http://core.tcl.tk/tcl/info/a0bc856dcd Have fun ;-) Harald -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
