similar to: delete content of directory - unlink doesn't work as expected

Hi, all, I'm looking a utility for removing a directory from within R. Currently, I'm using: foo <- function(...) { mydir <- tempdir() dir.create(mydir, showWarnings = FALSE, recursive = TRUE) on.exit(system(sprintf("rm -rf %s", mydir))) ## do some stuff in "mydir" invisible() } However, this is assumes "rm" is available. I know of

It seems unlink doesn't work with wildcards in 2.5.0. I've tried R-2.5.0 under gnu/linux from source and the Mac binary from att research. Example: > dir() [1] "bgx.Rnw" "bgx.pdf" "run.1" > unlink("run.*",recursive=T) > dir() [1] "bgx.Rnw" "bgx.pdf" "run.1" > unlink("run.1",recursive=T)

I was trying to remove a directory and couldn't figure out why it was failing: > dir("~/p4/r-packages/IREval/Users", recursive=T) [1] "u0048513/p4/r-packages/IREval/DESCRIPTION" [2] "u0048513/p4/r-packages/IREval/R/IREval.R" [3] "u0048513/p4/r-packages/IREval/Read-and-delete-me" [4] "u0048513/p4/r-packages/IREval/tests/general.R" >

unlink fails to remove symbolic links. This is more prominent now -- when a package creates symbolic links during installation, 00LOCK is not removed. Martin > setwd(tempdir()) > fl <- tempfile(); file.create(fl) [1] TRUE > lnFile <- tempfile(); system(paste("ln -s", fl, lnFile)) > list.files() [1] "file19495cff" "file74b0dc51" > unlink(fl);

!!! DON'T TRY THE CODE IN THIS EMAIL AT HOME !!! Well, unlink() does what it is supposed to do, so you could argue that there is nothing wrong with it. Also, nobody would call unlink() on "~", right? The situation is not so simple, however. E.g. if you happen to have a directory called "~", and you iterate over all files and directories to selectively remove some of them,

Hi Duncan, unlink is a C function, right ? why need a :: ?  Or is there a class ?   --- On Wed, 10/26/11, Duncan Sands <baldrick at free.fr> wrote: From: Duncan Sands <baldrick at free.fr> Subject: Re: [LLVMdev] LLVM build is failed giving Path.inc:714: error: ‘unlink’ was not declared in this scope To: llvmdev at cs.uiuc.edu Date: Wednesday, October 26, 2011, 11:10 AM Hi, if you

I see the default behavior of unlink with respect to directories is changing in 1.2. This causes me a certain amount of difficulty: since the recursive argument is not supported in S I will need to start building up my compatibility library again (which is almost empty now). Instead of changing unlink's default behavior it might be better to define a new function (perhaps Sys.rm) with the

https://bugzilla.samba.org/show_bug.cgi?id=7129 Summary: rsync 3.0.7 - unlink failed (21) - unable to delete directory Product: rsync Version: 3.0.7 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned at samba.org

Hello, I use the R command unlink(file, recursive = TRUE, force = TRUE) to delete folders, subfolders and files on Mac OS X. When I was running my script on a Windows computer I realised that for unlink there is no option/parameter "force". I do not know why but without that "force" option R cannot delete the subfolders/files. What can I do? -- View this message in

Does someone have a solution for this problem ? I am using gcc version 4.4.5 (Ubuntu/Linaro 4.4.4-14ubuntu5)  and I have tried several versions of LLVM including llvm 2.9 final. I am getting same error again and again. I have successfully build the llvm on another machine with gcc version of 4.3. Thanks in advance. make[1]: Entering directory

Hi, if you change unlink to ::unlink on that line, does it help? Ciao, Duncan. On 10/26/11 19:27, janarbek wrote: > Does someone have a solution for this problem ? > I am using gcc version 4.4.5 (Ubuntu/Linaro 4.4.4-14ubuntu5) and I have tried > several versions of LLVM including llvm 2.9 final. I am getting same error again > and again. > > I have successfully build the llvm

I was hoping that someone could try to reproduce an error that I am getting. The R Site Search keeps timing out on me, so apologies of this has already come up. I'm using > R.version _ platform i386-pc-mingw32 arch i386 os mingw32 system i386, mingw32

There was a patch merged in on 9/29 that changed remove() calls to unlink(): - (djm) Merged big SCO portability patch from Tim Rice <tim at multitalents.net> Does SCO's libc not include remove()? Note that sftp-server.c is currently using remove. The reason I ask is I'd like to keep the portable tree as close to openbsd as possible, and if we need remove() for SCO we should

Hi Rowland, Thanks for taking the time to look at this. I will post the log 10 output a bit later. Btw, what logs with log level 10 are you interested in? Here’s my samba config with sensitive info replaced with placeholders: [global] access based share enum = yes browseable = yes comment = <COMMENT> create mask = 0660 directory mask =

The patch does inseret unistd.h as below. However, I am still getting exactly same error when I do make.if you have any suggestions please let me know. #if HAVE_UNISTD_H #include <unistd.h> #endif   =========================================== Phone : 82-42-860-1838 Fax : 82-42-860-6790 Cell Phone: 82-10-7599-1981 =========================================== --- On Mon, 10/24/11, Eli

Yes, I applied the patch on trunk version like below. It says patching file. However, when I make, the build is still failing. janarbek at ubuntu:~/Work/llvm/llvm$ patch -p0 < unistd.txt patching file lib/Support/Unix/Path.inc   =========================================== Phone : 82-42-860-1838 Fax : 82-42-860-6790 Cell Phone: 82-10-7599-1981

The VALUE section in the help for 'unlink' says: | 0| for success, |1| for failure. Not deleting a non-existent file is not a failure, nor is being unable to delete a directory if |recursive = FALSE|. However, missing values in |x| result are regarded as failures. The last phrase doesn't make sense to me. Should it be either "missing values in x are regarded as

On Mon, Oct 24, 2011 at 5:10 PM, janarbek <canarbekmatay at yahoo.com> wrote: > > Yes, > > I applied the patch on trunk version like below. It says patching file. However, when I make, the build is still failing. > > janarbek at ubuntu:~/Work/llvm/llvm$ patch -p0 < unistd.txt > patching file lib/Support/Unix/Path.inc That means it was applied. In that case, I have

Hi, Can I get a brief description of all the FOPS in gluster or the location of the source code file so that I will try to get an understanding myself? Few FOPS I'm not clear like FORGET, UNLINK, FLUSH, LOOKUP Or is there a way I can tunnel through the FOPS that that are happening in the background for each operation? I have tried this to find from a brick logfile in TRACE mode, but there

Hello list, I have a apache documentroot with ownership root.www-data and mode 755 Now I have a /var/www/index.html and chown'd that file to user "foo". Sincen "foo" has no write permission under /var/www, he cannot rsync from remote server to the local filesystem because rsync will try to make temp file and unlink the original file before writing over it. Is there any