http://bugzilla.wpkg.org/show_bug.cgi?id=155
--- Comment #7 from Rainer Meier <r.me...@wpkg.org> 2009-04-25 02:05:34 --- I agree that the issue could be WHS-related. But knowing this makes no difference. I even think it's a bug and I don't care if it's a bug in WSH or windows execution subsystem in general (or it's broken by design). The effect is the same. Either WPKG has to find a very stable and portable work-around or we will keep it as a known issue that STDOUT/STDERR of the commands called cannot be flushed and the command might block when writing too much information to STDOUT/STDERR. Working around this issue is quite simple. Wrapping the command into a small CMD script which redirects STDOUT/STDERR to NUL or to any log works around the problem. In fact I thought about appending "> NUL 2>&1" to every command to make sure the output is sent to NUL. -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. ------------------------------------------------------------------------- wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/ _______________________________________________ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
