Opened 20 years ago
Last modified 18 years ago
#364 closed Bug report
Problem with NFS-mounted computers
|Reported by:||lafitteb||Owned by:|
|Keywords:||Cc:||lafitteb, Tim Kosse|
|Component version:||Operating system type:|
|Operating system version:|
FileZilla has a problem to expand paths of NFS-mounted
computers. Please see the following mail for details:
At 14:07 2003/07/01 +0200, you wrote:
Ok when I use the Command Prompt to download the file
there is no problem ! However, using my FTP
client "FileZilla" it is as I said in my previous email... It is
not working with files located in nmrpc0. When I click on
nmrpc0 (path being /usr/people/polymer/nmrdata/) my
FTP client put me under the patch "/polymer/nmr/" !
The path should have been /nmrpc0/data/polymer/nmr
so the problem is probably that your ftp-program does
not properly expand the
/usr/people/polymer/nmrdata/ symbolic link to that path.
In short, I think it is a bug.
Maybe FileZilla works if you connect
to /nmrpc0/data/polymer/nmr instead?
That path should not have to be expanded the same
way since the backup
computer is NFS-mounted on /nmrpc0/data.
Or use another ftp-program.
This problem was found in other FTP clients like
smartFTP. Two FTP clients which work without
problems: FTP-voyager and CoreFTP
This bug report has been closed due to inactivity and has possibly
already been solved.
You can reopen this report if the issue still exists in the
latest version of FileZilla (Server).