[kiofuse] [Bug 75324] Integrate KIO Slaves into file system using FUSE gateway

[Jason Straight]

https://bugs.kde.org/show_bug.cgi?id=75324

--- Comment #97 from Jason Straight <j.straight-kde at straights.net> ---
(In reply to Bo Simonsen from comment #95)
> (In reply to Nate Graham from comment #66)
> > Any update, Bo? :)
> 
> There are really issues with kiofuse. Tried to transfer a relatively big
> file, got me 6 mbit/s and intensive CPU load, with plain sftp I got 100
> mbit/s. I saw in the log
> 
> log_kio_sftp: seek, offset =  31170560
> log_kio_sftp: write, offset =  0 , bytes =  4096
> 
> So kio_sftp is called just to write 4K, because "cp" does it. KIO provides
> file_copy, file_move etc for these operations. FTP has shortcomings as well,
> because no seek is possible kiofuse is not able to mount the ftp kioslave. 
> I am quite sure an analysis will discover other shortcomings as well. I must
> say I am not really fan of inventing the wheel again here, maybe using
> existing fuse technology like sshfs is a better choice, or gvfs.

You're lucky. Most of the time my kio powered transfers just die. Single small
files are fine. If I copy anything large, like an entire folder, or an iso,
over ssh or smb, it almost always just dies.

I gave up on it. I just use nemo file manager for anything to do with remote
FS. It's too frustrating.

I know there are other features concerning KIO slaves that people don't want to
give up, when you cant do file operations with a file manager, that's kind of a
moot point.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.