Wow.
That's pretty ancient. That was my fuse_daemon binary used to unmount
MacFUSE filesystems when the system shut down. The process did
nothing aside from waiting for SIGTERM to come from launchd, and then
it took appropriate action.
In hindsight, using com.google.filesystems.fusefs was probably not a
good idea, as the code didn't come from Google, but I wanted to
clarify its association with MacFUSE. Looks like the binary no longer
exists in /usr/local/bin/fuse_daemon, so you should just *REMOVE* the
file at /Library/LaunchDaemons/com.google.filesystems.fusefs.plist.
If you still have an old version of NTFS-3G hanging around, PLEASE
remove it, as it's virtually impossible that still works properly
under Leopard, and might *actually* destroy some data, as it's so old.
Apologies,
- Paul
On Nov 8, 2007, at 4:12 PM, [EMAIL PROTECTED] wrote:
>
> HI,
> I have a little problem after upgrading to Leopard.
> I used an early version of MacFuse. Now Iget this error-Messages in
> the Console Window.
> Can anybody help me, please.
> 08.11.07 22:10:02 com.apple.launchd[1]
> (com.google.filesystems.fusefs[1232]) Exited with exit code: 1
> 08.11.07 22:10:02 com.apple.launchd[1] (com.google.filesystems.fusefs)
> Throttling respawn: Will start in 10 seconds
> 08.11.07 22:10:12 com.apple.launchd[1]
> (com.google.filesystems.fusefs[1233]) posix_spawnp("/usr/local/bin/
> fuse_daemon", ...): No such file or directory
>
> Regrds
> Chris
>
>
> >
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"macfuse-devel" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/macfuse-devel?hl=en
-~----------~----~----~----~------~----~------~--~---
