Re: [go-nuts] How to correctly use exec.Command and properly clean up all pipes

2023-02-06 Thread 'Lucas Christian' via golang-nuts
; > > > Lucas Christian > > Staff Software Engineer, Voice and SIP Connectivity > > On Fri, Feb 3, 2023 at 12:44 PM Ian Lance Taylor > wrote: > >> > >> On Fri, Feb 3, 2023 at 12:38 PM 'Lucas Christian' via golang-nuts > >> wrote: > >&

Re: [go-nuts] How to correctly use exec.Command and properly clean up all pipes

2023-02-03 Thread 'Lucas Christian' via golang-nuts
completeness is there an issue tracker it would be worth filing this off to? -- Lucas Christian Staff Software Engineer, Voice and SIP Connectivity On Fri, Feb 3, 2023 at 12:44 PM Ian Lance Taylor wrote: > On Fri, Feb 3, 2023 at 12:38 PM 'Lucas Christian' via golang-nuts > wrote: &

Re: [go-nuts] How to correctly use exec.Command and properly clean up all pipes

2023-02-03 Thread 'Lucas Christian' via golang-nuts
Apologies for reviving an old thread, but thought this might be the most efficient way to keep context. I'm looking at a similar issue Thomas encountered, but in this case I'm concerned about how to handle errors returned from StdoutPipe()/StderrPipe() and properly clean up after that. e.g.: