> -----Original Message----- > From: Worley, Dale (BL60:9D30) > Sent: Friday, October 24, 2008 2:03 PM > To: Beeton, Carolyn (CAR:9D60) > Cc: [EMAIL PROTECTED] > Subject: RE: [sipX-dev] Please review stdout/stderr intercept > patchonXECS-1423 > > > I can't quite tell from the patch, but it appears that the new code > *always* creates the pipes and sets stdout/stderr of the > child to feed the pipes, whereas the old code left > stdout/stderr unchanged. If the parent doesn't attempt to > read the pipes and the child produces output, the child will > now stall. So the default behavior is now different. >
Is it a problem if the default behaviour is different? The only user of launch/captureOutput/wait is the SipxProcessCmd. I can add another boolean to only create the pipes if the caller asks, but is this really necessary? Carolyn _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
