similar to: disappearing tempdir()

The main point of this discussion has been that deleting the tempdir() a fixed number of days after its creation is a problem. It should be deleted when the process that created it is done. R attempts to do this, but there are cases in which it does not so a backup is needed. Bill Dunlap TIBCO Software wdunlap tibco.com On Wed, Apr 26, 2017 at 8:46 AM, Brian G. Peterson <brian at

>>>>> <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, >> * whatever tempdir harvesting cron job the user has be made

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 directory too. It might still be useful if R could sometimes detect when

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

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 >

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, >

Related to this problem - from R-devel NEWS (https://cran.r-project.org/doc/manuals/r-devel/NEWS.html): * tempdir(check = TRUE) recreates the tmpdir() if it is no longer valid (e.g. because some other process has cleaned up the ?/tmp? directory). Not sure if there's a plan to make check = TRUE the default though. /Henrik On Wed, Nov 8, 2017 at 4:43 PM, William Dunlap via R-devel

'Writing R Extensions', section 1.1.5, in the part about a package's 'inst' directory, says that if NEW is in both the top level and in the inst directory, the in inst will be installed: Note that with the exceptions of INDEX, LICENSE/LICENCE and NEWS, information files at the top level of the package will *not* be installed and so not be known to users of Windows and macOS

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)

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

Hi, One of the functions I use needs to write to a temporary file, in the directory given by tempdir(). I want to change this from the standard one, as the file is too large for the drive. However, tempfile() doesnt seem to respect the environment variables when I change them with Sys.setenv(). In a fresh R-session: > Sys.getenv("TMP") [1]

On 26 April 2017 at 08:29, Duncan Murdoch wrote: | This seems like the wrong approach. The problem occurs as soon as the | tempdir() gets cleaned up: there could be information in temp files | that gets lost at that point. So the solution should be to prevent the | cleanup, not to continue on after it has occurred (as "check = TRUE" | does). This follows the principle that

>>>>> Dirk Eddelbuettel <edd at debian.org> >>>>> on Wed, 26 Apr 2017 08:40:38 -0500 writes: > On 26 April 2017 at 08:29, Duncan Murdoch wrote: > | This seems like the wrong approach. The problem occurs as soon as the > | tempdir() gets cleaned up: there could be information in temp files > | that gets lost at that point. So

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

Does setting the environment variable TMPDIR, before starting R, to a directory on a bigger file system help? On Linux I get % mkdir /tmp/RTMP-BILL % env TMPDIR=/tmp/RTMP-BILL R --quiet --vanilla > tempdir() [1] "/tmp/RTMP-BILL/Rtmppgowz4" > tempfile() [1] "/tmp/RTMP-BILL/Rtmppgowz4/file7ce36ec5cb1e" I don't know if there is an R-specific environment

Sorry if this is too off topic, but one of the things that happens when you use a *nix box is you have opportunities to do some nifty tricks with shell scripts and whatnot to help maintain your network. Sometimes, this comes at the expense of using the tools that come with some windows software and is the result of necessity. Other times, this comes because the "nifty" tools that come

>>>>> 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 > |

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

Signed-off-by: Matteo Cafasso <noxdafox@gmail.com> --- python/t/test830RHBZ1406906.py | 55 ++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 55 insertions(+) create mode 100644 python/t/test830RHBZ1406906.py diff --git a/python/t/test830RHBZ1406906.py b/python/t/test830RHBZ1406906.py new file mode 100644 index 000000000..62caf8ce1 --- /dev/null +++

The original file had a lot of trailing null bytes so I tried making a similar file with: tf <- tempfile(); file <- file(tf, "wb") for(i in 1:(2^15-1))writeBin(rep(as.raw(32:127), len=2^16), file) for(i in 1:(2^15-1))writeBin(rep(as.raw(0L), len=2^16), file) close(file) log2(file.size(tf)) #[1] 31.99996 Reading this with readLines() caused R-3.4.0 to segfault in Rf_con_pushback