tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Goyo <>
Subject Re: Can't move files using symbolic links (allowLinking=true)
Date Tue, 22 Mar 2011 08:32:52 GMT
Firstly, thanks for all your answers.

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 subdir we are symlinking (it is we should make more than one mount,
one for every subdir we need to link.
- We neither can make the symlink (or the mount) to the entire "origin" dir,
because the client demands that only certain subdirs should be moved to the
new drive.

It seems there's no an easy way...

2011/3/22 Caldarale, Charles R <>

> > From: André Warnier []
> > Subject: Re: Can't move files using symbolic links (allowLinking=true)
> > The perl documentation for rename() though, has this to say :
> >
> > perl itself being written in C, is usually pretty close to the C
> > library.  But maybe the above is a bit dated.
> No, the description is perfectly valid - for the rename function.
> > What I am getting at is : what if, for reasons of efficiency
> > (but not to the benefit of portability obviously) the developer
> > of this C application of which the OP does not have the source,
> > used a rename() call in order to move a file from one directory
> > to the other, instead of a copy-and-delete sequence ?
> Quite possible; as noted earlier, there is no move() API.  The C programmer
> has to understand the limitations of rename() and compensate for them where
> needed.  One could probably run strace to find out just what the program is
> doing.
>  - Chuck
> MATERIAL and is thus for use only by the intended recipient. If you received
> this in error, please contact the sender and delete the e-mail and its
> attachments from all computers.
> ---------------------------------------------------------------------
>  To unsubscribe, e-mail:
> For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message