similar to: fatal error unused tempdir

Hello, I am running R on XP Windows machine, and frequently I have enable to start R. I have this message: "Fatal Error: cannot find unused tempdir name". I don't know why. Thanks, in advance, for your help Sandrine Coelho

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

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

Dirk, Your message felt a bit antagonistic to me, or maybe I'm not understanding what you're trying to say. We all seem to agree that different configurations exist, and that some Linux distributions are configured to delete files in /tmp/ after a certain amount of time (seems to be 10 days for Arch Linux, not sure about Ubuntu or Debian). The question of how users of such distributions

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

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

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

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

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

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

Recent versions of Windows will remove empty directories from areas that Windows considers places for temporary files. It does not seem to matter how old they are; empty directories are found and removred c. once a day. I haven't seen any documentation on this feature but I think you can turn if off by disabling "Storage Sense" in Settings>System>Storage. This means that

Chiming in late on this thread... > > | Are there any packages which > > | would break if a call to 'tempdir' automatically recreated this > > | directory? (Or would it be too much of a performance hit to have > > | 'tempdir' check and even just issue a warning when the directory is > > | found not to exist?) > >

?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

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

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

Martin, Thanks for your work on this. One thing that seems to be missing from the conversation is that recreating the temp directory will prevent future failures when R wants to write a temp file, but the files will, of course, not be there. Any code written assuming the contract is that the temporary directory, and thus temporary files, will not be cleaned up before the R process exits (which

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

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