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". "target" was originally a regular directory, but, because of space restrictions, we have changed this folder for a symbolic link which points to another partition in an external drive. So, the path remains the same.
The machine is a Red Hat Linux release 7.1 (Seawolf). The server is launched with the same user who is owner of the directory. This directory has the following permissions: drwxr-xr-x And the symbolic link has all the permissions up. Using a terminal, we're able to copy from the first directory to the second directory without problems (it doesn't matter if we do through the symbolic link or directly). Let's write it a little bit clearer: 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 file when using the server application (although we can do it manually from the filesystem using the same user of the tomcat server). Any help? 2011/3/21 André Warnier <a...@ice-sa.com> > 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 http://tomcat.apache.org/whichversion.html > (and 4.1.18 is from 2003, as far as I can tell) > > > We stablished a symbolic link to another path. At first, tomcat didn't see >> this path through the symlink, but we searched for it and found the >> allowLinking=true feature. >> Now, it sees the path. However, and here comes the problem, it doesn't >> allow >> to move files to this path. >> We've tried to move files manually with the same user of tomcat and it >> works >> well, but it doesn't via the web application. Besides, this feature worked >> perfect before making this folder reachable through a symlink. >> >> > Can you explain more precisely what you mean by "moving files" ? (who is > doing the moving, from where to where, using what,..) > (and maybe also tell us which platform this Tomcat is running on, etc..) > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
