Deep sleep affected by MacFuse and SSHFS installation?

[GoogleCodeExporter]

Could MacFuse and SSHFS affect deep sleep performance?

I am trying to troubleshoot a deep sleep problem that appeared around the time 
of my MacFuse 
and sshfs installation. Restarting from a month-old clone fixes the problem, 
but I don't have a 
more recent clone and want to roll back.

I see:
1. no deep sleep on inactivity
2. mouse and keyboard disabled after mouse click wakeup

I have now uninstalled it with the uninstall script. What should I do to 
uninstall SSHFS? Any other 
steps I should take to roll back changes?

I installed:
MacFUSE-Core-0.1.9.dmg
sshfs-0.1.0.dmg

PS: the software did work and it was wonderful to see my linux server mounted 
on my desktop 
and have files transferred with date intact.

Original issue reported on code.google.com by michael....@gmail.com on 2 Feb 2007 at 3:26

[GoogleCodeExporter]

I'm not sure how MacFUSE could affect deep-sleep to begin with, but since you've
uninstalled MacFUSE Core it is worth a shot to see if it makes a differnce.  You
don't need to worry about the sshfs app in order to try and verify.  As long as 
you
don't try to run it then I'm sure it has no affect on the system.  Please 
reboot (to
clear out an existing loaded MacFUSE kernel extension) and then from the 
terminal do:

kextstat | grep fuse

If you don't see anything then you are fine; if you see a line that has
"com.google.filesystems.fusefs" then the kerenel module is still loaded somehow.

Either way please report back and let us know if this somehow fixed your 
deep-sleep
problem.

Original comment by inaddr...@gmail.com on 2 Feb 2007 at 7:07

[GoogleCodeExporter]

Thank you, there was nothing there.

Furthermore, having rebuilt my startup disk from an old clone, and reinstalled 
MacFuse and sshfs, I can confirm 
that they were apparently not the cause of my machine's sleeping problem. 

In fact, the machine will sleep with an SSH/SFTP server on the desktop and it 
can still be re-opened when the 
machine re-awakens. Too bad an alias of the server fails to find the original 
once the original has been 
unmounted...

Original comment by michael....@gmail.com on 4 Feb 2007 at 8:10

[GoogleCodeExporter]

Original comment by si...@gmail.com on 5 Feb 2007 at 1:03

• Changed state: Invalid

[GoogleCodeExporter]

>> Too bad an alias of the server fails to find the original once the original 
has been 
unmounted...

Try specifying a custom fsid (the 'fsid' option to mount_fusefs) to see if you 
can make aliases behave better. The 
fsid is used to identify the volume. Normally, MacFUSE uses an fsid based on 
which /dev/fuse device is being 
used, so it can change with every mount, making it look like a different volume.

Original comment by si...@gmail.com on 5 Feb 2007 at 1:08