Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror

Comment NetInfo stability Issues (Score 1) 89

In regard to the original article's issue, most of the NetInfo timeout issues that I have ever seen relate to the the NetInfo server being configured to gather information from a NetInfo parent. If no valid NetInfo parent exists the issues that the poster described will occur. I have resolved all of these issues by one of two solutions. The first as a previous respondent indicated was to turn off the option for the comptuer ( client or server ) to look for directory information in NetInfo. The second is to remove the 'serves' property under the the NetInfo path /machines/broadcasthost. Removing this property will prevent the NetInfo server from looking for a parent. In the Mac OS X server install that I have, there was an empty network NetInfo database. The serves property pointed to it ( with the NI path ../network ) as the the value on the 'serves' property. So removing the property will prevent the NetInfo database from continuing to look for a parent which either does not exist or is blank.
Many thanks go to www.darwinfo.org ( now www.opendarwin.org ) and the FAQ with answers from Mark Majka ( sp ? ) for answering this question for me.
I would agree that details on how NetInfo works exactly are very scant from Apple. And in answer to my NetInfo questions from an 'Apple Systems Engineer' was 'it just works'.
I would also recommend looking around for old NeXT NetInfo documents, as I have found a lot of useful information regarding the setup of NetInfo from them.

Slashdot Top Deals

"Home life as we understand it is no more natural to us than a cage is to a cockatoo." -- George Bernard Shaw

Working...