|
#1
| |||
| |||
| Rapidly cycling nibindd crash I get the following sequence of messages generated EVERY FEW SECONDS on the console: Formulating crash report for process nibindd7568 (com.apple.nibindd7568) Exited abnormally: Trace/BPT trap Throttling respawn: Will start in 9 seconds I don't need to be doing anything overt -- I can just sit and watch it scroll. All applications seems to behave normally, but I imagine that this never-ending cycles slows things down. The com.apple.nibindd.plist file reads: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>Label</key> <string>com.apple.nibindd</string> <key>OnDemand</key> <false/> <key>ServiceIPC</key> <false/> <key>ProgramArguments</key> <array> <string>/usr/sbin/nibindd</string> </array> </dict> </plist> Thanks for any suggestions! |
|
#2
| ||||
| ||||
| Strange... I assume that file is some sort of NetInfo file; perhaps to "bind" something... "ni" = "NetInfo", "bind" = "bind", "d" = "daemon". Was your computer ever hooked into a network with a directory service running? I found this article, which seems to imply that a NetInfo database has become corrupt somehow/somewhere: http://lists.apple.com/archives/Darw.../msg00092.html
__________________ Power Macintosh G4/500MHz "Yikes!" 10.4.11 Server • 1024MB • 3 x 120GB + 320GB • DVR-111D • 2 x Radeon 7000 PCI • 2 x 17" CRT MacBook 2.0GHz Core 2 Duo - White 10.5.5 • 2048MB • 80GB • CD-RW/DVD-ROM iPod Photo 60GB • iPod nano 1GB • AT&T DSL 6Mb/768k http://www.jeffhoppe.com |
|
#3
| |||
| |||
| Thanks for interpreting the nibindd acronym! This computer has logged on to networks at hotels, airports, etc, so I'm not sure about whether its ever been on a network where a directory service was running. What seems odd to me is that Leopard does away with Netinfo altogether, so maybe the problem is a legacy from something that was installed under Tiger or earlier. In any event, I have now tried trashing the nibindd.plist file, and things seem to be OK: no nibindd crash, and network access is fine. I guess I'll find out if there are repercussions to deleting that file! |
![]() |
| Thread Tools | |
|
|