-
Notifications
You must be signed in to change notification settings - Fork 29
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
Make LIST output compatible with FuseFS #8
Comments
OK, so I updated the code for the LIST command to behave like vsftp's LIST command output would look like. Now, curlftpfs (and other FuseFS clients) show proper directory contents and file dates. |
However, any file operation still fails. touch'ing, cp'ing... just silently freezes until some timeout. Not fully understood, what is going on here. When connecting to a vsftpd FTP Server, a Will investigate further. |
It seems that curlftpfs wants to open a second control connection for file operations like touch, cp, ... |
Thanks for your investigations and fixes ! |
I don't know their code structure and maybe it's a dumb idea... but maybe one could try to add an option to limit the number of concurrent connections. There is a "-s single thread" command line option but that doesn't prevent it from using more than one connection. |
Fuse FTP-FS (fuse filesystem) -- connection is OK but nothing is visible (neither are directories)
This empty result is probably due to the format of the LIST output -- the way it was implemented is not understood by FuseFS.
Second problem: FuseFS sends "LIST -a", the "-a" gets treated by the server as filename/dirname and it tries to list "cwd/-a" which fails.
Touch freeze... not sure what happens here.
The text was updated successfully, but these errors were encountered: