aboutsummaryrefslogtreecommitdiff
path: root/ChangeLog.rst
AgeCommit message (Collapse)Author
2021-08-30Fixup whitespace and configure CI to keep it that wayCam Cope
2021-06-08Released 3.7.2sshfs-3.7.2Nikolaus Rath
2021-01-19Workaround for mkdir on existing directory (#242)Peter Belm
Added a secondary check so if a mkdir request fails with EPERM an access request will be tried - returning EEXIST if the access was successful. This matches the correct behaviour expected by applications such as git. Co-authored-by: Peter Belm <peter.belm@dataalchemist.co.uk>
2020-11-09Released 3.7.1sshfs-3.7.1Nikolaus Rath
2020-01-03Released 3.7.0sshfs-3.7.0Nikolaus Rath
2019-11-27Disable buflimit workaround by default.Nikolaus Rath
The corresponding bug in OpenSSH has been fixed in 2007 (cf. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=365541#37), so this shouldn't be needed anymore.
2019-11-24Add support for using multiple connectionsTimo Savola
The -o max_conns=N option causes multiple SSH processes and response processing threads to be created. This means that e.g. reading a large file no longer blocks all access to the filesystem. The connection is chosen by checking the per-connection statistics: 1. Choose connection with least outstanding requests; if it's a tie, 2. choose connection with least directory handles; if it's a tie, 3. choose connection with least file handles; if it's a tie, 4. choose connection which has already been established. The implementation assumes that the max_conns values will be small; it uses linear search. Example benchmark: With single connection: $ sshfs -o max_conns=1,workaround=nobuflimit ebox: mnt $ cat mnt/tmp/bigfile > /dev/null & $ time find mnt > /dev/null real 1m50.432s user 0m0.133s sys 0m0.467s With multiple connections: $ ~/in-progress/sshfs/build/sshfs -o max_conns=5,workaround=nobuflimit ebox: mnt $ cat mnt/tmp/bigfile > /dev/null & $ time find mnt > /dev/null real 1m15.338s user 0m0.142s sys 0m0.491s This feature was implemented to large extend by Timo Savola <timo.savola@iki.fi>. Thanks to CEA.fr for sponsoring the remaining work to complete this feature and integrate it into SSHFS!
2019-11-03Released 3.6.0sshfs-3.6.0Nikolaus Rath
2019-10-19Added direct_io option (#173)sunwire
2019-04-13Released 3.5.2sshfs-3.5.2Nikolaus Rath
2019-04-08Gracefully handle multiple spaces in ssh_command option (#169)mssalvatore
When using the "ssh_command" option, commands with multiple spaces in a row will not be properly parsed. Example: Properly parsed: ssh_command = "ssh -o IdentityFile=~/.ssh/id_rsa" Improperly parsed: ssh_command = "ssh -o IdentityFile=~/.ssh/id_rsa" This commit changes the ssh_command parsing logic so that both of the above examples are considered valid and properly handled. Fixes: #114.
2019-01-04Also remap GID under non-MacOSClayton G. Hobbs
The manpage says that -o idmap=user maps the UID and GID, but it apparently only mapped the UID. The code was in place to map the GID as well, but it was hidden behind #ifdef __APPLE__. This commit removes those #ifdefs, and in a couple of cases the code inside an #else, to make the option behave as documented.
2018-12-22Released 3.5.1sshfs-3.5.1Nikolaus Rath
2018-08-28Released 3.5.0sshfs-3.5.0Nikolaus Rath
2018-08-01Port SSHFS to CygwinBill Zissimopoulos
2018-07-25Fix error return value from rename()Quentin Rameau
Fuse operations expect negated errno values.
2018-06-29Released 3.4.0sshfs-3.4.0Nikolaus Rath
2018-06-20Correct workaround condition for not using handle in sshfs_getattr (#127)Rian Hunter
In libfuse<3, when `fstat_workaround` was true, that meant to always use the `path` argument to resolve fgetattr instead of the supplied handle. Before this change, the logic was interpreting `fstat_workaround` to not use the `path` argument when it was true. This change reverts to the libfuse<3 behavior.
2018-06-18Make utimens(NULL) work correctlyDaniel Lublin
2018-06-09Add workaround to always pass a 0 mode when creating a file (#128)Josh Triplett
Add workaround to always pass a 0 mode when creating a file This works around servers that produce an error for any non-zero mode.
2018-04-29Released 3.3.2sshfs-3.3.2Nikolaus Rath
2017-10-25Released 3.3.1sshfs-3.3.1Nikolaus Rath
2017-09-26Ignore fstab-specific mount optionsNikolaus Rath
Fixes: #96.
2017-09-22Install manpage in man1/, not 1/Nikolaus Rath
Fixes: #95.
2017-09-20Released 3.3.0sshfs-3.3.0Nikolaus Rath
2017-09-20Dropped support for writeback cachingNikolaus Rath
As of kernel 4.14, the FUSE module's + writeback implementation is not compatible with network filesystems, and there are no imminent plans to change that. For more details, see https://marc.info/?l=fuse-devel&m=150592103107662&w=2 or As a consequence, the -o unreliable_append option has become obsolete as well. Fixes: #93 Fixes: #88 Fixes: #81
2017-09-20Add support for mounting from /etc/fstabNikolaus Rath
Fixes: #92.
2017-09-20Dropped support for autotools buildNikolaus Rath
It's just too much of a pain to maintain.
2017-09-20Updated manual page with missing options.Nikolaus Rath
Fixes: #82.
2017-08-06Released 3.2.0sshfs-3.2.0Nikolaus Rath
2017-08-06Re-enabled writeback cache.Nikolaus Rath
Fixes: #72.
2017-08-06Support O_APPEND.Nikolaus Rath
Fixes: #76.
2017-08-06Actually disable writeback cache, instead of just claiming to do so.Nikolaus Rath
2017-08-04Released 3.1.0sshfs-3.1.0Nikolaus Rath
2017-08-04Disable writeback cache for nowNikolaus Rath
Writeback cache seems to cause dataloss in some situations. We need to investigate this first. See https://github.com/libfuse/sshfs/issues/72.
2017-08-03Accept -o cache_* options for backward compatibility.Nikolaus Rath
Fixes: #73.
2017-07-12sftp_readdir_async(): don't access request when it may have been freedNikolaus Rath
Fixes: #7
2017-07-08Released 3.0.0sshfs-3.0.0Nikolaus Rath
2017-07-08Switch to libfuse 3.1.0Nikolaus Rath
libfuse 3.0.0 is rather new and not widely used yet, so requiring libfuse 3.1.0 right away shouldn't be a problem.
2017-07-08Switch to libfuse 3.0.Nikolaus Rath
2017-06-22Added unit tests and travis integrationNikolaus Rath
2017-06-20Added .rst suffix to ChangeLog.Nikolaus Rath
That way, programs are more likely to highlight the file correctly.