sorry for ignoring your post. avoiding a zero sleep is not the only problem i think, but the algorythm seems to get in some feedback loop where it starts sleeping shorter and shorter. i see thousands of zero sleep calls with this thing and the stats graph for syscalls makes a big bump and i would really like to understand why :)
-- cinap
--- Begin Message ---> Can anybody explain this fossil behaviour from the periodic code? what if 0 < t - ct < 1? wouldn't it be a good idea to replace the doubles with vlongs? and replace *1e-6 with /1000000? that would make 0 < t - ct < 1 impossible. - erik
--- End Message ---
