[go-nuts] process wait

This operation is not portable across supported OSes, so you need to use
package syscall directly.

--

A minimum-feature compatible library could be created, though if something
equivalent to wait isn't present on all platforms, it'd be pretty
inefficient to emulate.

Kevin Gillette
The OP kept responding off-list. This functionality in this case was
needed to port a non-go solution to go. The go solution is far easier
and more reliable (i.e. just have a goroutine monitor each process
specifically and react to exits).

ahhh sorry my bad.... I sisn't realized that I wasn't replying to all.
So yes I will go for a pure go solution. I will see how it goes :-)

- benoît

Benoit Chesneau <bchesneau@gmail.com>
writes:
Sure, let us know if something gets hard. That's often an indicator
of a better path one missed.

Benoit Chesneau <bchesneau@gmail.com>
writes:
Depending on what you're trying to do, there could be an easy way with
goroutines and channels or WaitGroups delivering the responses.

I seemed to have received this off-list. Bringing it back in case
anyone else has something to offer.
The only reason you'd worry about efficiency in supervising processes
is if you're polling, I'd think. Most of the time, the processes are
running and your app is idle.

I don't know why you'd not do the most obvious thing -- just spawn a
goroutine for every process you want to supervise and have it manage
that child. You can have a shared channel to send the results from all
of them, or do so in isolation or whatever.

One goroutine per process is pretty much required to achieve your goal
and it's likely the easiest way to do it and at least as efficient as
whatever you'd be doing to track the state of each process so you'd know
what died or emitted output anyway.