From: Raul Parolari Date: 2010-07-02T14:59:12+09:00 Subject: Re: Networking: select() blocks for seconds (> timeout) Mark T wrote: > Wow Raul, > You know how to write a thriller at least! > >> We are not running any more the experiment where this problem occurred, >> so I cannot say now if this fixed it. But thanks for the tip. > > Does this mean the story is unfinished? > > MarkT Mark, you made my day with your line. It will remain an unsolved thriller for a while; not only the experiment is not running any more (the structure that was moved is being replaced) but I am also leaving that work, and I will not have the chance to verify it. However, I can't stand the thought of leaving that story unfinished. It was so damning, because everything worked for 99% of the time, every packet delivered with millisecond precision by ruby 1.9.2 keeping the pace up perfectly with C/Assembler firmware, and then this "Time thief" appearing every hour and taking away chunks of 5 or 10 seconds... only a sudden flash of that conversation with the JPL engineer ("the GC misses Mars landing!") gave me a clue (and kept me sane, barely). I will recreate the example using 2 macs connected via Ethernet (I must rewrite the code though, as it stays with the company). I will use Ruby on one side and C on the other, and hopefully it will happen again; and then I will disable/enable the Gc (not that those statements fix anything as some seem to think, as they will just shift the problem from one place to another of the program, but they will indicate if it is the GC). I will let you know the outcome (in 2-3 weeks). I appreciated your note Raul Parolari raulparolari@gmail.com -- Posted via http://www.ruby-forum.com/.