New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with RMD and full path on vsftpd #6504
Comments
We expect the server to handle absolute paths correctly. Do you know if you are using the latest version of vsftpd available? |
latest is 2.3.5, I am using 2.3.0, because it is on Solaris and there is a precompiled package only for 2.3.0 available. |
maybe the problem is, that he is changing into the directory and trying to RMD it while he is still in it: \ |
Replying to [comment:5 Anhubert]: Good point, that is very possible. But the server has no reason to lock the directory and/or should handle this as it is a file system specific implementation detail. Can you report a bug against |
I already opened a ticket at vsftpd: (http://viki.brainsware.org/forum/thread/80) And I did a trace on the vsftp trace while trying to delete the directory and indeed:
The "Err11939 EINVAL" seems to be an error if you rmdir a busy directory |
I finally found out, that this is indeed a serious Bug! I tried it with an older version 3.4.1, there the problem does not occure, here the details:
So the difference is 3.4.1 is changing one directory up, before trying to delete:
Please fix that bug. |
Regardless of the current working directory the directory should be deletable according to the FTP protocol specification. This is a bug in vsftpd which is locking the directory. |
Hi all,
I have following issue:
I login with FTPs, create a directory
and then i delete it
now again, I create the directory
then I log out and log in again and try to delete that:
And I get
now again, I create a directory
change to that directory
and create a subdirectory
Now I want to delete that dir immediate
And again
It looks like Cyberduck is always using the complete path when doing
commands as seen above.
If I use Filezilla, it does
and that works
So who has the bug, who has the problem and how to solve it? Is there a way to tell Cyberduck not to use the complete path in every command?
The text was updated successfully, but these errors were encountered: