|[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]|
On 2006 May 31, at 1:32 AM, Jeffrey Johnson wrote:
For a variety of unfortunate reasons, it had to be installed that way to meet the requirements of the release.
The daemon does basically nothing until a user activates Dedicated Network Builds.
So, yes, it is by design and, yes, we consider it to be a bug and am working towards a different solution in a future release. No need to file a bug on this particular issue.
If you want to permanently disable it:
sudo launchctl unload -w /System/Library/LaunchDaemons/ com.apple.dnbobserver.plist
Just remember to re-enable it if you want to use DNB:
sudo launchctl load -w /System/Library/LaunchDaemons/ com.apple.dnbobserver.plist
Beware! Do not copy and paste this into Terminal. There should not be a space between /System/Library/LaunchDaemons/ and com.apple.dnbobserver.plist. It could completely hose your system.
I copy / pasted the unload line. And everything is running fine. I did check the Activity Monitor, and bfobserver is no longer running. Could the potential system hosing happen with a restart?
(goes off to back up important files).
Adin Hunter Baber
_______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
Visit the Apple Store online or at retail locations.
Copyright © 2011 Apple Inc. All rights reserved.