Re: [Rd] running R with users home dirs on a shared filesystems

Another thing to avoid are having multiple processes simultaneously access single sqlite3 database stored on NFS mount. From sqlite manual: “Your best defense is to not use SQLite for files on a network filesystem” So, if you configuring RStudio Server, ma

Re: [Rd] 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(

Re: [Rd] Build failure on powerpc64

No, that does not change the issue: arithmetic.c:180:26: error: initializer element is not constant 180 | static LDOUBLE q_1_eps = 1.L / LDBL_EPSILON; Tom On Fri, Dec 13, 2019 at 11:56 AM Serguei Sokol wrote: > Le 13/12/2019 à 17:06, Tom Callaway a écrit : > > arithmetic.c: > > static LD

[Rd] running R with users home dirs on a shared filesystems

Hi guys, I want to ask devel for who knows better - having multiple nodes serving users home dirs off the same shared network filesystem : are there any precautions or must-dos & must-donts in order to assure healthy and efficient parallel Rs running simultaneously - and I don't mean obvious stuff

Re: [Rd] tempdir() containing spaces breaks installing source packages

You might expand the scope of this a bit to include Windows usernames with non-ASCII characters in them. If I recall correctly, if you are logged under a Cyrillic UTF-8 name then R will not even start. We have seen this in the wild. Bill Dunlap TIBCO Software wdunlap tibco.com On Fri, Dec 13,

[Rd] tempdir() containing spaces breaks installing source packages

Hello everyone! Temp paths are used in system2() calls without shQuote() because they are assumed not to contain spaces. On Windows, GetShortPathName() is used to try to ensure that. Unfortunately, sometimes GetShortPathName() silently fails to return a 8.3 file path and gives a full path instead

Re: [Rd] Build failure on powerpc64

Le 13/12/2019 à 17:06, Tom Callaway a écrit : arithmetic.c: static LDOUBLE q_1_eps = 1 / LDBL_EPSILON; Just a thought: can it be that it's "1" which is at the origin of compiler complaint? In this case, would the syntax "1.L" be sufficient to keep it calm? Serguei. ___

Re: [Rd] Build failure on powerpc64

An excellent question. It is important to remember two key facts: 1. With gcc on ppc64, long doubles exist, they can be used, just not safely as constants (and maybe they still can be used safely under specific conditions?). 2. I am not an expert in either PowerPC64 or gcc. :) Looking at connecti

Re: [Rd] Build failure on powerpc64

> Tom Callaway > on Thu, 12 Dec 2019 14:21:10 -0500 writes: > Hi R folks, > Went to build R 3.6.2 for Fedora/EPEL and got failures across the board. > Disabling the test suite for all non-intel architectures resolves most of > the failures, but powerpc64 dies in the