Timeouts truncate memory image about lime HOT 4 CLOSED

Perhaps we need to adjust the default timeout. How long did it take you to collect memory?

can you try a timeout=5000 and see what happens?

from lime.

I've updated the default timeout to 5 seconds per page from 500 ms. Please let me know if this resolves your issues.

from lime.

With timeout=5000, I do not see the Reading is too slow. message in the kernel log.

That being said, why should any timeout apply to non-AWS acquisitions? If I'm reading issue #9 correctly, the timeout was introduced for the slow reads in AWS EC2 instances. Would a default of no timeout be appropriate? Or are most uses of LiME these days in AWS?

from lime.

First of all there's no guarantee that the timeout issue is unique to AWS. Secondly, there's no good way to detect that we're running an AWS instance. Finally, if it takes longer than 5 seconds to read/write 4 KiB of data, then something is horribly wrong anyway. You can always disable the option with timeout=0.

from lime.