Hi,
enclosed you will find an amend fix as replacement to
_sb-win-multi-worker-add-3.patch (just forgotten to save after
renaming NGX_SINGLE_WORKER - NGX_CONF_UNSET_PTR, before it was
commited).
18.06.2015 21:55, Maxim Dounin:
As I already tried to explain, the approach with inherited
So, in VM it work for me also.
I'm assuming that something on my windows work-pc has prevented to
inherit listener in this way (driver, LSPs installed (Layered Service
Providers), antivirus or something else)...
But, why don't you want to use a suggested solution of me?
If I will realize
Hello!
On Wed, Jun 17, 2015 at 09:58:46AM +0200, Sergey Brester wrote:
Yes, for exactly one child process...
The code in question uses the socket in two process, parent and
child.
For example, same (modified for multiprocessing) code does not work on my
mashine (win7 x64) for 2nd (3th
Hi,
Yes, for exactly one child process...
For example, same (modified for multiprocessing) code does not work on
my mashine (win7 x64) for 2nd (3th etc.) process (with error 10022 =
INVARG). I think the handle schould be then duplicated, and see MSDN
Hi,
enclosed a further changeset with backwards compatibility to 1 worker
processing (without inheritance as before fix), if single worker
configured + a little bit code review.
P.S. github updated also.
Regards,
sebres.
11.06.2015 15:03, Sergey Brester:
Hi,
I've forgotten to
Hi,
I've forgotten to free the shmem, thus enclosed an amendment with
clean-up, relative last changeset.
Regards,
sebres.
10.06.2015 21:48, Sergey Brester:
Hi,
enclosed you will find an attached changeset, that contains fix for windows
issue with multiple workers (once listening
