Because that's the communication protocol between the parent and child. There
is a difference between unsolicited exit and empty result exit.
Cheers,
Simon
> On May 20, 2019, at 11:22 AM, Sun Yijiang wrote:
>
> Have read the latest code, but I still don't understand why mc_exit
> needs to wri
Have read the latest code, but I still don't understand why mc_exit
needs to write zero on exit. If a child closes its pipe, parent will
know that on next select.
Best,
Yijiang
Tomas Kalibera 于2019年5月20日周一 下午10:52写道：
>
> This issue has already been addressed in 76462 (R-devel) and also ported
>
This issue has already been addressed in 76462 (R-devel) and also ported
to R-patched. In fact rmChild() is used in mccollect(wait=FALSE).
Best
Tomas
On 5/19/19 11:39 AM, Sun Yijiang wrote:
I've been hacking with parallel package for some time and built a
parallel processing framework with it.
I've been hacking with parallel package for some time and built a
parallel processing framework with it. However, although very rarely,
I did notice "ignoring SIGPIPE signal" error every now and then.
After a deep dig into the source code, I think I found something worth
noticing.
In short, wring
I've been hacking with parallel package for some time and built a
parallel processing framework with it. However, although very rarely,
I did notice "ignoring SIGPIPE signal" error every now and then.
After a deep dig into the source code, I think I found something worth
noticing.
In short, wring
