Unfortunately, the sshfs project has been unmaintained for some time and I don't have the resources to maintain both projects, macFUSE and sshfs. It would be better if SSHFS established the connection to the remote host first before mounting the volume. macFUSE does not know whether sshfs is simply dealing with a slow network connection or if the connection could not be established at all. macFUSE relays those file system operations to the sshfs process, which might not respond. Every mount triggers several file system requests from macOS system components, including Finder. In case this connection fails for any reasons, SSHFS does not handle incoming file system requests properly. SSHFS mounts virtual volumes before establishing the ssh/sftp connection to the remote host. In my tests I was able to mount SSHFS volumes on Ventura under /Volumes/sshfs without any issues. I don't think the SSHFS issues are specifically linked to Ventura. The freezes are a bit of a different story. When attempting to mount a volume on the same folder more than once in a row, make sure (between your mount attempts) that there are no lingering macFUSE mounts on the folder. This is a security mechanism enforced by macOS. Please raise this issue with pCloud's support team in case the latest pCloud release does not work for you on Did you check the permissions and ownership of /local_folder? If the folder is not owned by the user who runs the sshfs command the mount will fail.
Macfuse 10.13 update#
This means you will need to update pCloud to a version that adds support for Ventura. The recommended way of installing macFUSE is running the installer from pCloud uses a custom version of macFUSE. If you are using an older version, I recommend updating to the latest macFUSE release. First of all, macFUSE includes support for Ventura since version 4.4.0 which was released in June. It seems a couple of things are getting mixed up here.
0 kommentar(er)
