On 22-May-18 9:38 PM, Thomas Monjalon wrote:
22/05/2018 18:35, Anatoly Burakov:
When using --no-shconf option, the expectation is that no multiprocess
will be supported as no shared files are created. However, fbarray
still creates some shared files that prevent multiple processes with
the same
22/05/2018 18:35, Anatoly Burakov:
> When using --no-shconf option, the expectation is that no multiprocess
> will be supported as no shared files are created. However, fbarray
> still creates some shared files that prevent multiple processes with
> the same prefix from starting.
>
> Fix this by a
When using --no-shconf option, the expectation is that no multiprocess
will be supported as no shared files are created. However, fbarray
still creates some shared files that prevent multiple processes with
the same prefix from starting.
Fix this by avoiding creating shared files whenever noshconf
3 matches
Mail list logo
