, Charles R chuck.caldar...@unisys.com
From: André Warnier [mailto:a...@ice-sa.com]
Subject: Re: Can't move files using symbolic links (allowLinking=true)
The perl documentation for rename() though, has this to say :
rename OLDNAME,NEWNAME
perl itself being written in C, is usually pretty
On 22 March 2011 08:32, Goyo goyocas...@gmail.com wrote:
Inside origin there're about ten subdirs like target. Some of them are
symlinked to the new filesystem. The rest, must remain in their path so:
- AFAIK, we can't mount the new drive to origin/target because target is
not
the only
Goyo wrote:
Hi.
I need to use a symbolic link to access a certain path in my server, where
I'm using Jakarta Tomcat 4.1.18.
Oh, a real old-timer, he ? You know how old this is, right ? I think some people on this
list may still have been in primary school when it was released.
See
Yeah, it's a very old version. But we can't change it, anyway.
The details about the moving:
The application (written in C), first, generates a new file which is stored
in one directory, say origin. This step is perfectly made.
Then, the application moves this file to another directory
target.
On 21 March 2011 16:35, Goyo goyocas...@gmail.com wrote:
We want to move a file from origin/ to origin/target/
Previously, this movement was made perfect
Then, we change origin/target/ for a symlink called target which points to
another path in another partition.
Now, it doesn't move the
The (another) problem is that we can't access the source code :S
2011/3/21 Peter Crowther peter.crowt...@melandra.com
On 21 March 2011 16:35, Goyo goyocas...@gmail.com wrote:
We want to move a file from origin/ to origin/target/
Previously, this movement was made perfect
Then, we change
On 21 March 2011 17:36, Goyo goyocas...@gmail.com wrote:
The (another) problem is that we can't access the source code :S
*chuckle* Gotta love configurable code.
OK, so the issue is that you're short of space. How about mounting a
partition at origin/target? Or even origin, depending how short
Goyo wrote:
Yeah, it's a very old version. But we can't change it, anyway.
The details about the moving:
The application (written in C), first, generates a new file which is stored
in one directory, say origin. This step is perfectly made.
Then, the application moves this file to another
On 21 March 2011 20:39, André Warnier a...@ice-sa.com wrote:
Maybe a guess : under Unix/Linux, move (mv) is a rename, and it is not
the same as copy + delete original. And a move (rename) works as long
as the source and target are inside the same filesystem, but not if they are
on different
From: peter.crowth...@googlemail.com [mailto:peter.crowth...@googlemail.com]
On Behalf Of Peter Crowther
Subject: Re: Can't move files using symbolic links (allowLinking=true)
Maybe a guess : under Unix/Linux, move (mv) is a rename,
and it is not the same as copy + delete original
Caldarale, Charles R wrote:
From: peter.crowth...@googlemail.com [mailto:peter.crowth...@googlemail.com] On
Behalf Of Peter Crowther
Subject: Re: Can't move files using symbolic links (allowLinking=true)
Maybe a guess : under Unix/Linux, move (mv) is a rename,
and it is not the same as copy
André Warnier wrote:
Caldarale, Charles R wrote:
From: peter.crowth...@googlemail.com
[mailto:peter.crowth...@googlemail.com] On Behalf Of Peter Crowther
Subject: Re: Can't move files using symbolic links (allowLinking=true)
Maybe a guess : under Unix/Linux, move (mv) is a rename
From: André Warnier [mailto:a...@ice-sa.com]
Subject: Re: Can't move files using symbolic links (allowLinking=true)
The perl documentation for rename() though, has this to say :
rename OLDNAME,NEWNAME
perl itself being written in C, is usually pretty close to the C
library. But maybe
13 matches
Mail list logo