similar to: help.start() directory?

>>>>> Dirk Eddelbuettel <edd at debian.org> >>>>> on Sun, 23 Apr 2017 09:15:18 -0500 writes: > On 21 April 2017 at 10:34, frederik at ofb.net wrote: > | Hi Mikko, > | > | I was bitten by this recently and I think some of the replies are > | missing the point. As I understand it, the problem consists of these > |

On 26/04/2017 4:21 AM, Martin Maechler wrote: >>>>>> <frederik at ofb.net> >>>>>> on Tue, 25 Apr 2017 21:13:59 -0700 writes: > > > On Tue, Apr 25, 2017 at 02:41:58PM +0000, Cook, Malcolm wrote: > >> Might this combination serve the purpose: > >> * R session keeps an open handle on the tempdir it creates, >

Hi Mikko, I was bitten by this recently and I think some of the replies are missing the point. As I understand it, the problem consists of these elements: 1. When R starts, it creates a directory like /tmp/RtmpVIeFj4 2. Right after R starts I can create files in this directory with no error 3. After some hours or days I can no longer create files in this directory, because it has been

On Tue, Apr 25, 2017 at 02:41:58PM +0000, Cook, Malcolm wrote: > Might this combination serve the purpose: > * R session keeps an open handle on the tempdir it creates, > * whatever tempdir harvesting cron job the user has be made sensitive enough not to delete open files (including open directories) Good suggestion but doesn't work with the (increasingly popular)

The iso is needed in the build directory for autotest.sh to work when running as part of autobuild. This enhances autobuild.sh to copy it over after the rpms are built. Signed-off-by: Mike Burns <mburns at redhat.com> --- autobuild.sh | 13 +++++++++++++ 1 files changed, 13 insertions(+), 0 deletions(-) diff --git a/autobuild.sh b/autobuild.sh index fb9de92..aeee7dd 100755 ---

Hello, I run R 1.9.1 on a Windows XP machine. In the last week, I have started to get the following error message (about 85% of the time) when I attempt to start R: "Fatal error: cannot find unused tempdir name" I get this message whether I attempt to start R in interactive or batch mode. Looking at the help-manual description of tempdir didn't provide me with any obvious clues

On 21/04/17 14:03, Prof Brian Ripley wrote: > From the R-admin manual ?5: > > 'Various environment variables can be set to determine where R creates > its per-session temporary directory. The environment variables TMPDIR, > TMP and TEMP are searched in turn and the first one which is set and > points to a writable area is used. If none do, the final default is /tmp > on

>>>>> Henrik Bengtsson <henrik.bengtsson at gmail.com> >>>>> on Fri, 30 Mar 2018 10:14:04 -0700 writes: > So, the proposal would then be to write to tempdir(), > correct? If so, I see three alternatives: > 1. explicitly use file.path(tempdir(), filename), or > tempfile() everywhere. I think it should clearly be '1.',

Dear friends of R, I want to produce a pdf file with the contents of a matrix. I employ the latex command in combination with dvi, both contained in the Hmisc package. It seems to me that the function does not correctly set the directory. > tbl.loc <- matrix(1:4, nc=2) > latex.obj <- latex(tbl.loc) > dvi(latex.obj) warning: extra args ignored after 'cd' H:\PROJECTS\data

I was looking at the CRAN package 'bfork-0.1.2', which exposes the Unix fork() and waitpid() calls at the R code level, and noticed that the help file example for bfork::fork removes R's temporary directory, the value of tempdir(). I think it happens because the forked process shares the value of tempdir() with the parent process and removes it when it exits. This seems like a

On 26/04/2017 10:39 AM, Tomas Kalibera wrote: > > I agree this should be solved in configuration of > systemd/tmpreaper/whatever tmp cleaner - the cleanup must be prevented > in configuration files of these tools. Moving session directories under > /var/run (XDG_RUNTIME_DIR) does not seem like a good solution to me, > sooner or later someone might come with auto-cleaning that

>>>>> Jeroen Ooms <jeroenooms at gmail.com> >>>>> on Tue, 25 Apr 2017 15:05:51 +0200 writes: > On Tue, Apr 25, 2017 at 1:00 PM, Martin Maechler > <maechler at stat.math.ethz.ch> wrote: >> As I've found it is not at all hard to add an option >> which checks the existence and if the directory is no >>

I think recreating tempdir() is ok in an emergency situation, but package code should not be removing tempdir() - it may contain important information. Bill Dunlap TIBCO Software wdunlap tibco.com On Wed, Nov 8, 2017 at 4:55 PM, Henrik Bengtsson <henrik.bengtsson at gmail.com > wrote: > Related to this problem - from R-devel NEWS >

The other day I was working on an example which used tempfile() to create file for use by the graphics device. And while I love tempfile()---as it is portable and clever and the files get cleaned by R and all that---I noticed one missing feature I would like to see: beside a starting name pattern, and an optional directory, an 'file extension' argument would be nice to have. As e.g. in

Temporary files not accessed for a long time are automatically removed in some Linux distributions and probably other operating systems too, depending on system configuration. This may affect the per-session temporary directory, the path of which is returned by tempdir(). I think it would be nice if R automatically tried to recreate a missing tempdir() but this could have some performance

I was writing Rd documentation for a new package when I came across this issue. Here's the smallest example: > library(tools) > cat("\\examples{x <- '<%=rnorm(1)%>'}\n",file=file.path(tempdir(),'test.Rd')) > readLines(file.path(tempdir(),'test.Rd')) [1] "\\examples{x <- '<%=rnorm(1)%>'}" >

?tempdir says By default, ?tmpdir? will be the directory given by ?tempdir()?. This will be a subdirectory of the temporary directory found by the following rule. The environment variables ?TMPDIR?, ?TMP? and ?TEMP? are checked in turn and the first found which points to a writable directory is used: if none succeeds ?/tmp? is used. Unfortunately, it doesn't seem to

Hello R-Help I have a question about the "behind the scenes" behaviour of the Rscript -e command and particularly its interaction with Sweave and tempdir(). We are trying to deploy R as a web service to do water quality analyses and have been writing software to call Sweave via Rscript eg: cmd> Rscript -e Sweave('sweavefile.Rnw') One problem we have been having is that

Full_Name: Tom Callaway Version: 2.7.2 OS: Fedora 10 (Linux/x86_64) Submission from: (NULL) (96.233.67.230) Recently, Debian identified a security issue with the javareconf script in R. I confirmed that this is still unfixed in R 2.7.2. The following patch resolves the issue: diff -up R-2.7.2/src/scripts/javareconf.BAD R-2.7.1/src/scripts/javareconf --- R-2.7.2/src/scripts/javareconf.BAD

Hi, all. I noticed recently that llvm::sys::fs::createTemporaryFile does not use llvm::sys::path::system_temp_directory, instead relying on its platform-specific helper TempFile. Is there any reason for this disparity? The two implementations are not in sync, either: - TempDir honors TMPDIR, TMP, TEMP, TEMPDIR, and a configuration-settable P_tmpdir on Unix-y systems. system_temp_directory just