search for: r_unlink

The call to system() probably is an internal call used to delete the session's tempdir(). This sort of failure means that a potentially large amount of disk space is not being recovered when R is done. Perhaps R_CleanTempDir() could call R_unlink() instead of having a subprocess call 'rm -rf ...'. Then it could also issue a specific warning if it was impossible to delete all of tempdir(). (That should be very rare.) > q("no") Breakpoint 1, R_system (command=command at entry=0x7fffffffa1e0 "rm -Rf /tmp/RtmppoKPXb...

...replacement for Unix. The details are complicated on Unix as well as on Windows. And re reusing existing implementations, we will have to check they do exactly what we need about signals, terminal, process groups, termination, input and output, etc. It may also be that improving performance of R_unlink() would be easier, as it is rather un-optimized now. So I just wanted to buy time with (possibly temporary) fix in 83851. Thanks Tomas >

...lap <williamwdunlap at gmail.com> wrote: >> The call to system() probably is an internal call used to delete the session's tempdir(). This sort of failure means that a potentially large amount of disk space is not being recovered when R is done. Perhaps R_CleanTempDir() could call R_unlink() instead of having a subprocess call 'rm -rf ...'. Then it could also issue a specific warning if it was impossible to delete all of tempdir(). (That should be very rare.) >> >>> q("no") >> Breakpoint 1, R_system (command=command at entry=0x7fffffffa1e0 &qu...

...ap <williamwdunlap at gmail.com> wrote: > > The call to system() probably is an internal call used to delete the session's tempdir(). This sort of failure means that a potentially large amount of disk space is not being recovered when R is done. Perhaps R_CleanTempDir() could call R_unlink() instead of having a subprocess call 'rm -rf ...'. Then it could also issue a specific warning if it was impossible to delete all of tempdir(). (That should be very rare.) > > > q("no") > Breakpoint 1, R_system (command=command at entry=0x7fffffffa1e0 "rm -Rf /...

Hello, This is probably a very minor point, but R_CleanTempDir may still have a shell injection in it. I couldn't find a way to shoot the user in the foot in a significant way (by, say, accidentally removing ~), thanks to R disallowing spaces in the path, but if Sys_TempDir somehow acquires a value of "/tmp/';echo;'", R_CleanTempDir() will remove /tmp instead of its

...etpwuid and getgrgid which can be expensive if the user/group database are held on a network. Note that file_test ALSO uses file.info for the same purpose Suggest rebuilding file_test to use ‘stat’ based call for directory search, and using file_test in function library. Note that functions like R_unlink uses stat calls to determine if something is a directory. -Alex Brown *Detail:* While developing an application using Shiny my (large fortune500) company started to have network issues and NIS performance issues in particular. Shiny will relatively frequently restart R, which entails loading a...

...williamwdunlap at gmail.com> wrote: >>>> The call to system() probably is an internal call used to delete the session's tempdir(). This sort of failure means that a potentially large amount of disk space is not being recovered when R is done. Perhaps R_CleanTempDir() could call R_unlink() instead of having a subprocess call 'rm -rf ...'. Then it could also issue a specific warning if it was impossible to delete all of tempdir(). (That should be very rare.) >>>> >>>>> q("no") >>>> Breakpoint 1, R_system (command=command at...

...lt;williamwdunlap at gmail.com> wrote: > >> The call to system() probably is an internal call used to delete the session's tempdir(). This sort of failure means that a potentially large amount of disk space is not being recovered when R is done. Perhaps R_CleanTempDir() could call R_unlink() instead of having a subprocess call 'rm -rf ...'. Then it could also issue a specific warning if it was impossible to delete all of tempdir(). (That should be very rare.) > >> > >>> q("no") > >> Breakpoint 1, R_system (command=command at entry=0x7...

Dear R-developers, Some of the more fat scripts (50+ GB mem used by R) that I am running, when they finish they do quit with q("no", status=0) Quite often it happens that there is an extra stderr output produced at the very end which looks like this: Warning message: In .Internal(quit(save, status, runLast)) : system call failed: Cannot allocate memory Is there any way to avoid this