|
|
heh
In case you were curious, my dual 800 G4 compiled in all of 6 minutes.
Anyway, unfortunate that it builds without threads support. Probably due to the lackluster pthreads implementation in darwin. Fortunately, it is coming, but probably not for 6 months.
One error, though - your startup item should NOT go in /System/StartupItems, everything in the System/ folder is for apple. It should be in /Library/StartupItems.
From here:
"The system startup items (that is, those provided by Apple) are located in /System/Library/StartupItems. You should not modify the items in this directory. However, you can also define your own startup items; these custom startup items are stored in /Library/StartupItems. See "Customizing Booting Behavior" for instructions on how to create your own startup items."Also, i understand lookupd also has its own cache. How much advantage will bind offer over lookupd's own cache? -B
lookupd
Now that my eyes have rolled back into their sockets...
I find it amusing when people whip out complex and time consuming solutions for problems that don't really exist -- just because they existed in UNIX-world and they know a few tricks.
lookupd has its own sophisticated caching mechanism. Here's the first two paragraphs from the man pages:
The lookupd daemon acts as an information broker and cache. It is called by various routines in the System framework to find information about user accounts, groups, printers, e-mail aliases and distribution lists, computer names, Internet addresses, and several other kinds of information. lookupd keeps a cache of recently located items to improve system performance. It also implements a search strategy used to find information from the many information sources that are potentially available to a computer. These include the Domain Name System (DNS), Sun Microsystem's Network Information Services (NIS), Apple's NetInfo system, and a set of files found in the /etc directory. X.500-style databases that implement the schema described in RFC 2307 may be accessed using the LDAP protocol.
lookupd cache vs caching
For the record: I'm very envious of your dual 800 G4....
There are basically four key differences between Caching DNS and lookupd (there are actually more, but you'd have to read DNS and BIND to understand them). They basically add up to the fact that lookupd's caching mechanism is rather rudimentary compared to bind's. At any rate, the key differences are as follows:
Granted, these are not large differences, but this is why I stated at the outset that this is a slight optimization. I did it on my machine because I was interested in tooling around with the new version (v. 9) of bind. Once I completed it, I figured it would be fun to share. As for flumingan and his rolling eyes (see previous reply): The pedantic tone of his email is more consistent with one who "existed in the UNIX[sic]-world and ... know[s] a few tricks" than he realizes. If he had read more than the first paragraphs of the man page for lookupd, then he'd have known at least the first three of the above four items. At any rate, he'll do well not to openly flaunt run-of-the-mill Unix knowledge as though it were proof that he knows the secrets of the universe; it makes him look silly. |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.15 seconds |
|