From: <no...@so...> - 2001-09-07 23:40:48
|
Bugs item #219255, was opened at 2000-10-25 22:04 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=110894&aid=219255&group_id=10894 Category: 26. Channel Types Group: = 8.3.1 Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) >Assigned to: Andreas Kupries (andreas_kupries) Summary: Closing a pipe to a busy process blocks even when -blocking Initial Comment: OriginalBugID: 5924 Bug Version: 8.3.1 SubmitDate: '2000-06-20' LastModified: '2000-09-11' Severity: CRIT Status: Assigned Submitter: lfb ChangedBy: davidg RelatedBugIDs: 710 OS: Windows NT FixedDate: '2000-10-25' ClosedDate: '2000-10-25' Closing a pipe to a busy process blocks on Windows even after you have turned blocking off on the channel. Try running this script in a tclsh on Windows: set pipe [open "| tclsh.exe doforever.tcl" r+] fconfigure $pipe -blocking 0 close $pipe Contents of doforever.tcl: while {1} {} Expected Result: The primary process closes the pipe and does not block. Actual Result: The primary process blocks. We discovered this problem in the Ajuba2 Server process pool. If we try to close the pipe to a busy interpreter, the server blocks. -- A related bug was fixed on the Unix side, but the Windows side uses a different sort of closedown functions. Has to be further investigated. -- 09/06/2000 hobbs ---------------------------------------------------------------------- >Comment By: Andreas Kupries (andreas_kupries) Date: 2001-09-07 16:40 Message: Logged In: YES user_id=75003 Rather bug #219252 after renumbering tango. ---------------------------------------------------------------------- Comment By: Donal K. Fellows (dkf) Date: 2001-01-09 07:20 Message: See also Bug #119252 ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=110894&aid=219255&group_id=10894 |