Closed GoogleCodeExporter closed 8 years ago
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
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
Original comment by si...@gmail.com
on 5 Feb 2007 at 1:03
>> 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
Original issue reported on code.google.com by
michael....@gmail.com
on 2 Feb 2007 at 3:26