Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm running an Apache webserver with name-based virtual hosting. I've set up the necessary blocks, etc. Since I wish to test this out without actually buying domain names, I've altered my Mac's internal DNS (I'm on OS X Tiger). I did this using the technique described in, using a string of commands of which the last was sudo niload -v hosts / < hosts.

Everything has been working fine for months. Now, as I've begun to learn about NetInfo, I see that all of the name-ip pairs that I've defined show up in this application. Is there any burning reason that I should use niload, instead of using NetInfo from now on?


share|improve this question

niload and NetInfo both provide a way to interact with the NetInfo database. You can use either or. To quote from man niload:

niload loads information from standard input into the given NetInfo domain.

So niload is what you want to use in scripts or on the command line, NetInfo if you're looking for a GUI.

If you plan on upgrading to Leopard (10.5) or Snow Leopard (10.6) in the future it's worth noting that NetInfo has been replaced by Directory Services (dscl on the command line) and there is not equivalent of NetInfo

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.