Skip to content
Prev 7245 / 63424 Next

multi-threaded R current status?

Thanks for the status report.  I'm a firm believer in creating tools to
automate pesky repetitive tasks.

Once the core of R is reentrant/thread-safe, perhaps it would be possible to
get 90% of the way to fully reentrant/thread-safe by modifying  .C /
.Fortran / friends to include a lock that prevent more than one thread at a
time from accessing functions within the same library (unless, of course,
the library is flagged as thread-safe.)
Yes, I've already been thinking about security.  For the moment, I'm
building this tool strictly for trusted environments where security
shouldn't be a problem, and I'm not directly exposing R commands to the end
user.  

Still, I'm already running the server as 'nobody' to lessen the potential
for trouble, and I've been considering how to run this within a chroot jail
which contains only the necessary files to run R.   

R has a *lot* of features that allow access to the underlying system and
that could potentially be used to do nasty things, particularly if the user
is allowed to provide arbitrary R code.  Of course, so do all of our
favorite CGI languages.  That's part of what makes them useful ;^) 

-Greg
http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html
_._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._.
_._