Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the '10.4: Prevent repetitive system.log entries from Fusion' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.4: Prevent repetitive system.log entries from Fusion
Authored by: njvm on Mar 18, '07 10:22:01PM

Unfortunately, this solution did not work for me. I am using Beta 2 of Fusion. Running the command disables the error messages in the System log but then when I log-on to Fusion I have no network connectivity. Also, when I re-boot and open Fusion again everything is ok, eg I have network connectivity, but the error messages to the System log have again started up. Any ideas? I am using my Airport card to connect to the network.



[ Reply to This | # ]
10.4: Prevent repetitive system.log entries from Fusion
Authored by: tanjiee on Mar 21, '07 11:45:23PM
Bummer. The fact remains that even with the Fusion beta 2, the logging continues to be an issue. Something interesting I found in this Virtualization wiki http://wiki.osx86project.org/wiki/index.php/Virtualization

basically, they suggest that when not using vmware, we should run the command to stop the logging. I should notice that the command is a bit different. And, since I tried both, the following command actually works without giving error messges (cannot find.... type of error) The following is a direct quote from the page

When you're not using Fusion, stop the network kexts with

sudo '/Library/Application Support/VMware Fusion/boot.sh' --stop

and when you want to use Fusion again, resume the services with

sudo '/Library/Application Support/VMware Fusion/boot.sh' --start

You can also rotate the logs more frequently (so they don't have time to get as big), see the thread for details.

hope this helped someone

[ Reply to This | # ]