OS X 10.5 server error: The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Over the weekend, I installed MacFUSE Core 10.5-1.1.1 on my Leopard server 
running Mac OS 
X 10.5.1. The server software is running on an Intel iMac. I have tried to use 
MacFUSE from my 
MacBook Pro to mount a shared server volume. The laptop is running Leopard 
client (10.5.1) 
installed. A week ago I successfully used the same laptop running the same OS 
to mount a share 
volume on a Tiger server (a different machine) running OS X 10.4.10. I made no 
configuration 
change to the laptop after changing servers. Checking the Google site, I noted 
reference to the 
forked error on this URL:

http://code.google.com/p/iphonedisk/issues/detail?id=3

2. Because I wasn't been able to mount any 10.5.1 server shares using my 
laptop, I uninstalled 
MacFUSE from the server using the recommended Terminal command. 

sudo /Library/Filesystems/fusefs.fs/Support/uninstall-macfuse-core.sh 

I can't get rid of the error even after a reboot. The error message does not 
appear in the Console 
log that's stored on my laptop.

What is the expected output? What do you see instead?

Every five seconds my server's Console log is populated with several instances 
of the this error 
message:

The process has forked and you cannot use this CoreFoundation functionality 
safely. You MUST 
exec().

What version of the product are you using? On what operating system?

MacFUSE Core 10.5-1.1.1 on OS X Server 10.5.1 and OS X Client 10.5.1

Please provide any additional information below.

Original issue reported on code.google.com by kom...@pacbell.net on 3 Dec 2007 at 6:46

[GoogleCodeExporter]

This error isn't something unique to MacFUSE--it can come from ANY program that 
does a certain set of things that were OK on 
Tiger but not on Leopard.

Even with MacFUSE, this will show up ONLY at mount-time and ONLY if you try to 
run the Tiger version of MacFUSE on Leopard. 
That's not what you are doing here.

Besides, MacFUSE doesn't run any daemons itself, so even if it were installed 
(which it isn't since you uninstalled it), there's 
nothing in it that would cause this error every five seconds.

Original comment by si...@gmail.com on 3 Dec 2007 at 7:35

[GoogleCodeExporter]

I meant to add in my previous message:

How do you know this is coming from MacFUSE?

Original comment by si...@gmail.com on 3 Dec 2007 at 7:41

[GoogleCodeExporter]

I am having this problem too, just starting today--not sure what has changed.  
I get a bunch of this:

Dec  5 14:20:11 zombi [0x0-0x35035].com.google.sshfs[441]: The process has 
forked and you cannot use this 
CoreFoundation functionality safely. You MUST exec().

Original comment by chiller...@gmail.com on 5 Dec 2007 at 10:26

[GoogleCodeExporter]

[0x0-0x35035].com.google.sshfs[441] is NOT coming from any of the software that 
I distribute from this page. 
You must have something else installed (Macfusion?).

Both issue reporters, please (re)read the following:

The error message you are seeing can only come if you run the Tiger version of 
MacFUSE (or related software) on 
Leopard. Any other software that depends on MacFUSE may need to be recompiled 
(*WILL* need to be 
recompiled if you see this error message).

Original comment by si...@gmail.com on 5 Dec 2007 at 10:45

[GoogleCodeExporter]

I checked the Console logs extensively and I have not been able to pinpoint the
source of the error that's being reported by my Leopard server. It's apparent 
that I
installed a Tiger version of a piece of software on my server. However, I cannot
determine what that program is. I have MacFusion 1.2 installed on my laptop but 
not
on my server. The laptop that is running the client version of Leopard doesn't
generate this error. The server error is not a show-stopper. From my 
perspective, you
can close this issue.

Original comment by kom...@pacbell.net on 6 Dec 2007 at 6:35

[GoogleCodeExporter]

Original comment by si...@gmail.com on 8 Dec 2007 at 9:46

• Changed state: Invalid