hostconfig process

[John C. Welch]

On 8/15/07 11:26 AM, "Martin Costabel" <costabel at wanadoo.fr> wrote:

>> bill, and it wouldn't matter. However, for Mac OS X client, I'd not use
>> scutil anyway, but rather networksetup, as it's got a much cleaner way to go
>> about this.
> 
> /usr/sbin/networksetup exists on Mac OS X server. On Tiger client, it
> comes in two flavors, networksetup-jaguar and networksetup-panther (how
> clean is that on Tiger?), the latter symlinked to networksetup; but you
> won't see it if you don't happen to have
> /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Support
> in your PATH.

If you just use 
/System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Support/
networksetup, you automatically get the proper one for your OS. You just
fully path it, and bob's your uncle.

> 
> Together with its brother systemsetup, this is a promising candidate for
> the "worst-documented and most obscure Mac OS X command" contest.

Huh? It's rather fully documented, and it's hardly obscure. It's also found
on every default install of the OS since 10.3

> 
> Anyway, you can't set the hostname with it, only the computername.
> Dan's scutil --set HostName, although also undocumented, has the
> advantage of working.

Well, that depends if it's setting the hostname at the same time as the
computer name. (I forget, and I honestly don't feel like checking) Of
course, if your DNS has different ideas about the hostname for that IP
address, then that will probably override things anyway.

-- 
John C. Welch         Writer/Analyst
Bynkii.com              Mac and other opinions
jwelch at bynkii.com