Re: Luasocket select/timeout problems on UDP

[Jim Mellander <jmellander@...>]

Jim Mellander wrote:
> Diego Nehab wrote:
> <snip>
>
> > Did you notice how fast these packets arrive? If select is blocking
> > until timeout, they should come every second. If select returns whenever
> > a packet arrives, they should come every 1/2 second. What is it in your
> > system? As I said, on Linux and on Mac OS X, this works, and the packet
> > messages come every 1/2 second.
> >
> > Regards,
> > Diego.
>
> I modified flood.lua to send n bytes when it is sending to 
> datasources[n], and modified server.lua to print the unix timestamp, now 
> I get:
>
>
> 1144798013 Binding to host '127.0.0.1' and port 8081...
> 1144798013 Waiting for packets on 127.0.0.1:8081...
> 1144798013 Binding to host '127.0.0.1' and port 8082...
> 1144798013 Waiting for packets on 127.0.0.1:8082...
> 1144798013 Binding to host '127.0.0.1' and port 8083...
> 1144798013 Waiting for packets on 127.0.0.1:8083...
> 1144798013 Binding to host '127.0.0.1' and port 8084...
> 1144798013 Waiting for packets on 127.0.0.1:8084...
> 1144798013 Binding to host '127.0.0.1' and port 8085...
> 1144798013 Waiting for packets on 127.0.0.1:8085...
> 1144798013 Packet received from 127.0.0.1/1365 1 bytes
> 1144798013 Packet received from 127.0.0.1/1365 1 bytes
> 1144798014 Packet received from 127.0.0.1/1365 1 bytes
> 1144798014 Packet received from 127.0.0.1/1365 2 bytes
> 1144798014 Packet received from 127.0.0.1/1365 3 bytes
> 1144798014 Packet received from 127.0.0.1/1365 4 bytes
> 1144798014 Packet received from 127.0.0.1/1365 1 bytes
> 1144798014 Packet received from 127.0.0.1/1365 2 bytes
> 1144798014 Packet received from 127.0.0.1/1365 3 bytes
> 1144798014 Packet received from 127.0.0.1/1365 4 bytes
> 1144798015 Packet received from 127.0.0.1/1365 1 bytes
> 1144798015 Packet received from 127.0.0.1/1365 2 bytes
> 1144798015 Packet received from 127.0.0.1/1365 3 bytes
> 1144798015 Packet received from 127.0.0.1/1365 4 bytes
> 1144798016 Packet received from 127.0.0.1/1365 1 bytes
> 1144798016 Packet received from 127.0.0.1/1365 2 bytes
> 1144798016 Packet received from 127.0.0.1/1365 3 bytes
> 1144798016 Packet received from 127.0.0.1/1365 4 bytes
> 1144798016 Packet received from 127.0.0.1/1365 1 bytes
> 1144798016 Packet received from 127.0.0.1/1365 2 bytes
> 1144798016 Packet received from 127.0.0.1/1365 3 bytes
> 1144798016 Packet received from 127.0.0.1/1365 4 bytes
> 1144798017 Packet received from 127.0.0.1/1365 1 bytes
> 1144798017 Packet received from 127.0.0.1/1365 2 bytes
> 1144798017 Packet received from 127.0.0.1/1365 3 bytes
> 1144798017 Packet received from 127.0.0.1/1365 4 bytes
> 1144798017 Packet received from 127.0.0.1/1365 1 bytes
> 1144798017 Packet received from 127.0.0.1/1365 2 bytes
> 1144798017 Packet received from 127.0.0.1/1365 3 bytes
> 1144798017 Packet received from 127.0.0.1/1365 4 bytes
>
> The timing seems faster than expected, and the 5th expected datasource 
> is not seem.  Does this give any insight into the problem?

Actually, I guess the timing is OK, since we're sleeping for .5 secs 
after sending all packets, but the 5th datasource is being skipped.

BTW - I have luasocket compiled to use the poll syscall instead of 
select, in hopes of fixing my problem, but so far, no luck...


--
Jim Mellander
Incident Response Manager
Computer Protection Program
Lawrence Berkeley National Laboratory
(510) 486-7204

Your fortune for today is:

The goal of science is to build better mousetraps.  The goal of nature
is to build better mice.