Today I commented out the DYLD_LIBRARY_PATH entry in my /etc/bashrc file, rebooted and lo and behold, Macfusion works again.Īh well, another fine theory completely demolished by reality. Running the sshfs command in terminal worked, after passing the error mentioned in the Apple discussion thread above. I do have DLYD_LIBRARY_PATH set in my environment. In 10.8 something got left on in the kernel compile so that DLYD_ warnings are emitted when a sudo or other setuid programs are run, see: The returns form the sshfs commands are not being properly parsed, I think. What is the ideal solution in this case do you think? I mean, I have no idea what it does, but I am disinclined to simply remove it. This environment variable is probably useful though. On Nov 15, 2012, at 5:04 PM, Alex Regueiro wrote: Oct 18 14:36:57 macfusionAgent : debug1: identity file /Users/johnson/.ssh/id_rsa type -1 Oct 18 14:36:57 macfusionAgent : debug1: Connection established. Oct 18 14:36:57 macfusionAgent : debug1: Connecting to port 22. Oct 18 14:36:57 macfusionAgent : debug1: Reading configuration data /etc/ssh_config Oct 18 14:36:57 macfusionAgent : debug1: Reading configuration data /Users/johnson/.ssh/config Oct 18 14:36:57 macfusionAgent : sshfs: cannot find sshnodelay.so

Oct 18 14:36:56 macfusionAgent : Task launched OK Oct 18 14:36:56 Macfusion : Note status changed for fs (kalendaetest) to Waiting to Mount Oct 18 14:36:56 macfusionAgent : Mounting Oct 18 14:34:32 Macfusion : Prefs update FSEvents callback received Oct 18 14:34:32 macfusionAgent : Prefs update FSEvents callback received Here is the log entry for a failed connection:

Macfusion not working in sierra