similar to: running R with users home dirs on a shared filesystems

User home is not used by R directly, so it is really up to whatever package/code may be using user home. In our setup we have all machines using NFS mounted homes for years. From experience the only thing to watch for are packages that use their own cache directories in $HOME instead of tempdir() - it is technically against CRAN policies but we have seen it in the wild. Cheers, Simon > On

Hi All, I am working on a POC that I''d like to show a group of 10 to 15 folks. I was wondering if sqlite would do for db with about 20 people hitting on the application. Does sqlite locking the entire db while writing manifest itself in such scenario? Regards, Kashyap

Hi, at moment I have this environment: CentOS nginx + phpfpm Dovecot, with Maildir format Postfix Roundcube MySQL backend about 10000 mailusers dual core Intel(R) Pentium(R) D CPU 3.00GHz 8 GB RAM network storage device (Coraid), ext4 file system I have no performance issue now, but I need to move to a different server: FreeBSD 10.1-RELEASE nginx + phpfpm Dovecot Postfix Roundcube dual

hi everyone an attempt to set up a cluster, I'm reading around and see some howto writers would say to put "private dir on the FS cluster" - one question I have: is this correct? necessary? I have partial success, I get: $ ctdb status Number of nodes:2 pnn:0 10.5.6.32 OK pnn:1 10.5.6.49 UNHEALTHY (THIS NODE) Generation:323266562 Size:2 hash:0 lmaster:0 hash:1

hi everyone a good basher around here? I try in a script: _rdiffBack="rdiff-backup -v5 --tempdir /tmp/ --no-eas --exclude-other-filesystems --exclude-symbolic-links" _rdffiExclude="--exclude '**/~*' --exclude '**.tmp' --exclude-regexp '(.glusterfs|.trashcan|temp)'" _execCom=${!2} _sourceDir=${1} _backupTo=${3} __backMeUp() { for _sourceDir in

On 16/03/17 16:38, Marc Muehlfeld via samba wrote: > Hi, > > Am 15.03.2017 um 15:39 schrieb lejeczek via samba: >> something like this: >> >> [big] >> path = /data/big >> writeable = no >> >> [my.big] >> path = /data/big/my >> writeable = yes >> >> [your.big] >> path = /data/big/your >> writeable = yes >>

hi everyone something like this: [big] path = /data/big writeable = no [my.big] path = /data/big/my writeable = yes [your.big] path = /data/big/your writeable = yes is such a configuration healthy? What are possible negative implications this may cause, if any? ver. 4.4 many thanks, L

hi guys in my qutest I have this: ...     <filesystem type='mount' accessmode='passthrough'>       <source dir='/home'/>       <target dir='/home'/>     </filesystem> ... and on the host /home/* are user home dirs which are automounted off a glusterfs volume. The guest starts okey, I can see dirs under /home but if I go to /home/userA I

Hi Dirk, One side observation: r-cran debian now seems to be in Ubuntu 20.10 Universe so I don't need to add the repo any more. Here is a reproducible example that fails with the latest r-cran-rcppparallel but works when I manually install the source package: require(rstan) stancode <- 'data {real y_mean;} parameters {real y;} model {y ~ normal(y_mean,1);}' mod <-

I maintain a directory structure containing dirs and files that I regularly push to ~50 hosts, which are divided into 3 groups that have slightly different needs (minor mods in a couple of files). So ideally I would have 4 directories: /path/to/sync/common/ <- common files /path/to/sync/group1/ <- group1 specific only /path/to/sync/group2/ <- group2 specific only

On 09/11/16 23:28, Martin Schwenke via samba wrote: > On Wed, 9 Nov 2016 16:05:32 +0000, lejeczek via samba > <samba at lists.samba.org> wrote: > >> an attempt to set up a cluster, I'm reading around and see >> some howto writers would say to put "private dir on the FS >> cluster" - one question I have: is this correct? necessary? > No, this is not

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)

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

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

Harold, I've taken a closer look at your example and I'd call this an Sweave bug. It creates tempfiles each time you run it, and doesn't delete them at the end. For example: > list.files(tempdir()) character(0) > testfile <- system.file("Sweave", "Sweave-test-1.Rnw", package = "utils") > Sweave(testfile, out="junk.tex")

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)%>'}" >

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

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