Re: [R] [FORGED] file.exists() on device files

2017-01-13 Thread Jeff Newmiller
Of course they have separate criteria for determining existence... they do different things, and therefore have different requirements for access permissions. -- Sent from my phone. Please excuse my brevity. On January 13, 2017 3:54:35 AM PST, Benjamin Tyner wrote: >Thank you for the insights,

Re: [R] [FORGED] file.exists() on device files

2017-01-13 Thread Benjamin Tyner
Thank you for the insights, Rolf and Henrik. To give another example, this time in non-interactive mode, Rscript -e "file.exists(commandArgs(TRUE))" <(echo "Hi") [1] TRUE versus Rscript -e "normalizePath(commandArgs(TRUE))" <(echo "Hi") [1] "/dev/fd/63" Warning message: In n

Re: [R] [FORGED] file.exists() on device files

2017-01-11 Thread Rolf Turner
On 12/01/17 16:33, Henrik Bengtsson wrote: FYI, the /proc is there because Unix has something called the "proc filesystem (procfs; https://en.wikipedia.org/wiki/Procfs) is a special filesystem in Unix-like operating systems that presents information about processes and other system information

Re: [R] [FORGED] file.exists() on device files

2017-01-11 Thread Henrik Bengtsson
On Wed, Jan 11, 2017 at 3:56 PM, Rolf Turner wrote: > On 11/01/17 23:12, Benjamin Tyner wrote: >> >> Hi, >> >> On my linux machine (Ubuntu, and also tested on RHEL), I am curious to >> know what might be causing file.exists (and also normalizePath) to not >> see the final device file here: >> >>

Re: [R] [FORGED] file.exists() on device files

2017-01-11 Thread Rolf Turner
On 11/01/17 23:12, Benjamin Tyner wrote: Hi, On my linux machine (Ubuntu, and also tested on RHEL), I am curious to know what might be causing file.exists (and also normalizePath) to not see the final device file here: > list.files("/dev/fd", full.names = TRUE) [1] "/dev/fd/0" "/dev/fd/1"