Re: Luasocket select/timeout problems on UDP

[Jim Mellander <jmellander@...>]

I modified server.lua again to print the allegedly readable sockets, and 
to print out if no datagram was actually available - it only seems to 
see 1, 2, & 3 out of the 5 that it should be seeing.  Additionally, when 
flood.lua is killed, the sockets 1 & 2 still are returned by select as 
readable

1144870525 Packet received from 127.0.0.1/3009 1 bytes
1144870525 Packet received from 127.0.0.1/3009 2 bytes
1144870525 Packet received from 127.0.0.1/3009 3 bytes
1144870525 Readable sockets are: 1 2 3
1144870526 Packet received from 127.0.0.1/3009 1 bytes
1144870526 Packet received from 127.0.0.1/3009 2 bytes
1144870526 Packet received from 127.0.0.1/3009 3 bytes
1144870526 Readable sockets are: 1 2 3
1144870527 Socket says readable, but no dgram on 1
1144870527 Packet received from 127.0.0.1/3009 2 bytes
1144870527 Packet received from 127.0.0.1/3009 3 bytes
1144870527 Readable sockets are: 1 2 3   <-- flood.lua killed.
1144870528 Socket says readable, but no dgram on 1
1144870529 Socket says readable, but no dgram on 2
1144870529 Packet received from 127.0.0.1/3009 3 bytes
1144870529 Readable sockets are: 1 2
1144870530 Socket says readable, but no dgram on 1
1144870531 Socket says readable, but no dgram on 2
1144870531 Readable sockets are: 1 2
1144870532 Socket says readable, but no dgram on 1
1144870533 Socket says readable, but no dgram on 2
1144870533 Readable sockets are: 1 2
1144870534 Socket says readable, but no dgram on 1
1144870535 Socket says readable, but no dgram on 2
1144870535 Readable sockets are: 1 2
1144870536 Socket says readable, but no dgram on 1
1144870537 Socket says readable, but no dgram on 2
etc.

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

Your fortune for today is:

He hadn't a single redeeming vice. -- Oscar Wilde