 |
 |
Installing 10.2.3 update kills NetInfo on startup
|
 |
|
 |
|
Professional Poster
Join Date: May 2000
Location: Urbandale, IA
Status:
Offline
|
|
I was doing a housecall at someone's house this evening; they just purchased a new eMac, and it arrived with 10.2.0 installed. I brought along a copy of the 10.2.3 combined standalone updater and ran it, not expecting any problems.
Upon restarting, the eMac hung waiting for Directory Services. I started it up in Verbose mode and sure enough, the NetInfo daemon was crashing during startup. Not good.
I repaired permissions from the 10.2.0 CD that came with the machine and it fixed a few permissions on some important-looking files, but the machine still refused to boot.
I finally gave up and did an Archive-and-Install (preserving Users) to bring the eMac back to 10.2.0, but I'm curious as to what was going on.
Any clues?
|
|
"Yields a falsehood when preceded by its quotation" yields a falsehood when preceded by its quotation.
|
| |
|
|
|
 |
|
 |
|
Professional Poster
Join Date: May 2000
Location: Urbandale, IA
Status:
Offline
|
|
I should note that I'm sure the 10.2.3 updater is responsible. The machine was turned on for the first time just a day or two before Christmas, and the machine's owners haven't installed anything.
|
|
"Yields a falsehood when preceded by its quotation" yields a falsehood when preceded by its quotation.
|
| |
|
|
|
 |
|
 |
|
Senior User
Join Date: May 2001
Location: Boston, MA
Status:
Offline
|
|
This happened on my G4 too... there was a kbase article that said how to turn off unneeded directory services with the directory access program. Also make sure the ethernet adapter is not set to acquire address with bootp or it will search for a netinfo server every time the machine starts.
|
|
|
| |
|
|
|
 |
|
 |
|
Professional Poster
Join Date: May 2000
Location: Urbandale, IA
Status:
Offline
|
|
Originally posted by OpenStep:
This happened on my G4 too... there was a kbase article that said how to turn off unneeded directory services with the directory access program. Also make sure the ethernet adapter is not set to acquire address with bootp or it will search for a netinfo server every time the machine starts.
Thanks, but I'm pretty sure that's not it. The problem wasn't that NetInfo was taking a long time looking for a remote parent to bind to, but that it was outright crashing. Also, this was a stock install, so neither NetInfo nor the Directory Access app had been modified to do anything like that.
As for the ethernet adapter looking for an IP address: the machine was booting past that point; in verbose mode, I noticed that it registered its hardware address, noted that it had no connections, and went away.
(Last edited by Oneota; Dec 29, 2002 at 12:02 PM.
)
|
|
"Yields a falsehood when preceded by its quotation" yields a falsehood when preceded by its quotation.
|
| |
|
|
|
 |
 |
|
 |
|
|
|
|
|

|
|
 |
Forum Rules
|
 |
 |
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
|
HTML code is Off
|
|
|
|
|
|
 |
 |
 |
 |
|
 |