Displaying 20 results from an estimated 10000 matches similar to: "unlink: parameter "force" not available in R windows version"
2006 Nov 28
3
delete content of directory - unlink doesn't work as expected
Hi,
I try to delete the files in a directory. While the command
invisible(lapply( list.files( "DeleteThis" ), function(x)
file.remove(paste("DeleteThis", x, sep="/" )) ))
works, I keep thinking that there should be a more direct command.
"unlink" looks like a good candidate but whith this I only arrive to
either delete the whole directory or nothing
2007 Apr 25
2
R-2.5.0 and unlink/wildcards
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)
2010 Oct 04
1
Globbing inconsistencies, dir() vs. unlink()
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"
>
2009 Mar 21
1
unlink fails to remove symbolic links
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);
2000 Oct 10
2
unlink in 1.2
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
2020 Feb 26
3
unlink() on "~" removes the home directory
!!! 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,
2011 Oct 26
0
[LLVMdev] LLVM build is failed giving Path.inc:714: error: ‘unlink’ was not declared in this scope
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
2000 Dec 18
3
SCO remove() and unlink()
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
2011 Oct 26
0
[LLVMdev] LLVM build is failed giving Path.inc:714: error: ‘unlink’ was not declared in this scope
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
2011 Oct 26
2
[LLVMdev] LLVM build is failed giving Path.inc:714: error: ‘unlink’ was not declared in this scope
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
2006 Aug 17
1
unlink disables help?
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
2011 Oct 25
2
[LLVMdev] LLVM build is failed giving Path.inc:714: error: ‘unlink’ was not declared in this scope
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
2011 Oct 25
3
[LLVMdev] LLVM build is failed giving Path.inc:714: error: ‘unlink’ was not declared in this scope
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
2011 Oct 25
0
[LLVMdev] LLVM build is failed giving Path.inc:714: error: ‘unlink’ was not declared in this scope
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
2009 Nov 11
2
typo in docs for unlink()
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
2017 Nov 13
2
What is the difference between FORGET and UNLINK fops
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
2002 Oct 28
2
Fwd: rsync and unlink permission
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
2017 Nov 13
0
What is the difference between FORGET and UNLINK fops
Filtering the brick logs in TRACE mode with rpcsvc.c does show the FOPS.
>From this, I've realized that LOOKUP is actually dns lookup. This actually
differs from NFS lookup operation. Please correct me if I'm wrong.
Regards,
Jeevan.
On Nov 13, 2017 9:40 PM, "Jeevan Patnaik" <g1patnaik at gmail.com> wrote:
> Hi,
>
> Can I get a brief description of all the
2000 Dec 20
1
unlink() is not synchronized with existing connections (PR#783)
> # creating a file
> cat("sddfasdf", file="tempfile")
> showConnections()
class description mode text isopen can read can write
> con <- file("tempfile", "r")
> readLines(con)
[1] "sddfasdf"
Warning message:
incomplete final line in: readLines(con, n, ok)
> showConnections()
class description mode text isopen
2011 Oct 24
2
[LLVMdev] LLVM build is failed giving Path.inc:714: error: ‘unlink’ was not declared in this scope
Hello All,
I am getting following error on Ubuntu. My gcc is gcc version 4.4.5. Please let me know if you have any comments/suggestions.
In file included from /home/janarbek/Work/llvm/llvm/lib/Support/Path.cpp:299:
/home/janarbek/Work/llvm/llvm/lib/Support/Unix/Path.inc: In member function ‘bool llvm::sys::Path::eraseFromDisk(bool, std::string*) const’: