un semblant de solution, si cela vient de launchd
"I just had a little problem occur with the use of launchctl. I was looking to reduce the amount of memory used on my system, and found a server process (bfobserver) that was using a great deal of real memory. On checking, I found in the developer's Read Me that this process is not needed if you are not using xgrid compilation. Great. I will stop it from starting. I used launchctl to change its startup via launchd with the following command:
- Code:
-
sudo launchctl unload -w \
/System/Library/LaunchDaemons/com.apple.dnbobserver.plist
The problem was I accidentally put a space between /System/Library/LaunchDaemons/ and com.apple.dnbobserver.plist. The result was a wild card to launchctl for that directory, and caused all of the daemons listed to be killed and all the daemon startups were disabled. This meant that the system was now unusable, and a reboot just ended in a blue screen.
To fix this, I had to come up in single user mode (Command-S on startup). Remount the root file system read/write, compare all of the LaunchDaemon entries with my other system, and then re-enable them. This was a time consuming and stupid mistake, but easily done."
source :
http://www.macosxhints.com/article.php?story=20061110220558563