On Nov 18, 10:55 am, MRAB wrote:
> On 18/11/2011 15:48, Junfeng Hu wrote:
>
>
>
>
>
> > Thanks
> > Yes, I had tried this before, so you could find that I comment the line
> > sock.setsockopt(socket.SOL_SOCKET, socket.SO_REUSEADDR, 1)
> > Here is the results.
> > D:\Python test>mythread2.py
> > Tra
On 18/11/2011 15:48, Junfeng Hu wrote:
Thanks
Yes, I had tried this before, so you could find that I comment the line
sock.setsockopt(socket.SOL_SOCKET, socket.SO_REUSEADDR, 1)
Here is the results.
D:\Python test>mythread2.py
Traceback (most recent call last):
File "", line 1, in
File "C:\P
On Sat, Nov 19, 2011 at 3:11 AM, Junfeng Hu wrote:
> Hi Chris.
> The socket only binded once. That's the problem I'm puzzleing, I think it may
> a bug of multiprocessing in windows, or something I missed.
I don't know how multiprocessing goes about initializing those
subprocesses; I suspect that
Hi Chris.
The socket only binded once. That's the problem I'm puzzleing, I think it may a
bug of multiprocessing in windows, or something I missed.
--
http://mail.python.org/mailman/listinfo/python-list
On Sat, Nov 19, 2011 at 2:51 AM, Junfeng Hu wrote:
> And actually ,the socket hadn't been used in this script.
Doesn't matter that you haven't used it; you're binding to the port,
that's what causes the 10048.
I think the main problem is that you're trying to share sockets across
processes, but
And actually ,the socket hadn't been used in this script.
--
http://mail.python.org/mailman/listinfo/python-list
Thanks
Yes, I had tried this before, so you could find that I comment the line
sock.setsockopt(socket.SOL_SOCKET, socket.SO_REUSEADDR, 1)
Here is the results.
D:\Python test>mythread2.py
Traceback (most recent call last):
File "", line 1, in
File "C:\Python27\lib\multiprocessing\forking.py",
On Fri, Nov 18, 2011 at 9:23 PM, Junfeng Hu wrote:
> Hi All, I'm trying to leverage my core i5 to send more UDP packets with
> multiprocssing, but I found a interesting thing is that the socket.bind is
> always reporting 10048 error even the process didn't do anything about the
> socket.
> sock
I did a test on linux, it works well, so the issue is related to os.
--
http://mail.python.org/mailman/listinfo/python-list
