Never mind, I found the issue - contrary to the documentation Linux does modify
tv in the call to select() so our measure of elapsed time doesn't increase.
Work-around now present in R-devel.
Cheers,
Simon
On Jul 12, 2011, at 5:23 PM, Simon Urbanek wrote:
>
> On Jul 12, 2011, at 4:22 PM, Jer
On Jul 12, 2011, at 4:22 PM, Jeroen Ooms wrote:
>> Can you please verify the behaviour is still the same in a recent R-devel or
>> at least R-2.13.1? And that there was no other already answered request on
>> R-help or R-devel re. timeouts?
>
> The code below is R 2.13.1. It shows that the timeo
> Can you please verify the behaviour is still the same in a recent R-devel or
> at least R-2.13.1? And that there was no other already answered request on
> R-help or R-devel re. timeouts?
The code below is R 2.13.1. It shows that the timeout time is more
than 3 minutes, although it was set to 5
?connections tells us:
"Note that this is a timeout for no response, not for the whole operation."
And indeed, it will take roughly 20 seconds rather than 60 - at least on
the Linux machine I tried it on with R-2.13.1.
Best,
Uwe Ligges
On 12.07.2011 14:24, jeroen00ms wrote:
According to
According to the download.file manual the timeout of a connection can be set
using options(timeout=10). This seems to work as expected on windows, but on
linux the connection does not timeout. I reproduced the problem both 0on
R-2.13 on Ubuntu and on R-2.12.1 on CentOS, but not in Windows.
> optio
