Re: [Rd] Signal handling / alarm timeouts

From: Henrik Bengtsson <>
Date: Tue, 12 Apr 2011 16:22:05 -0700

On Tue, Apr 12, 2011 at 3:58 PM, Murray Stokely <> wrote:
> What are the ramifications of setting up user signal handling to allow
> the use of e.g. alarm(2) to send a SIGALRM to the R process at some
> number of seconds in the future to e.g. interrupt a routine that is
> taking too long to complete.
> I can't find any R language support for this (e.g. a timeout argument
> to tryCatch() would be ideal), so am wondering what kinds of problems
> are to be expected if I do this with native C code in a package.
> Are there other ways to accomplish timeouts for blocks of R code like this?

See R help thread 'Time out for a R Function' on 2010-12-06 []. As explained there, R provides setTimeLimit(), which is cross platform so you don't have to rely on OS-specific signals. In R.utils there is evalWithTimeout(), which utilizes setTimeLimit().


>               - Murray
> ______________________________________________
> mailing list
> mailing list Received on Tue 12 Apr 2011 - 23:24:47 GMT

Archive maintained by Robert King, hosted by the discipline of statistics at the University of Newcastle, Australia.
Archive generated by hypermail 2.2.0, at Wed 13 Apr 2011 - 02:11:00 GMT.

Mailing list information is available at Please read the posting guide before posting to the list.

list of date sections of archive