hostconfig process

[Dan Shoop]

On Aug 11, 2007, at 4:04 PM, Jerry LeVan wrote:

>
>>
>> --------------------------------------------------------------------- 
>> -
>>
>> Message: 1
>> Date: Fri, 10 Aug 2007 16:06:09 -0700
>> From: "Justin C. Walker" <justin at mac.com>
>> Subject: Re: hostconfig process
>> To: omniadmin OSX <macosx-admin at omnigroup.com>
>> Message-ID: <FAED86C8-BF06-46FF-A6EA-8A9347EC13A2 at mac.com>
>> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
>>
>>
>> On Aug 10, 2007, at 11:11 , R.L. Grigg wrote:
>>
>>> Theres a remote OSX 10.4.10 system that I administor by ssh, and
>>> after I modify /etc/hostconfig, what process do I need to kill -HUP
>>> to have it read up the new settings so I dont have to reboot it
>>
>> You need to reboot to have this file re-scanned.  In essence, it
>> provides a lot of basic settings for the system (processes that may
>> run only at boot-time, or long-lived processes that have nothing to
>> do with the boot process) to use, and without restarting the whole
>> system, you won't get what you want.
>>
>> This may have changed in recent releases, but AFAIK, this is the
>> still the case.
>>
>> Justin
>>
>
> Have you tried "hostname -s newnane" (and setting the host name in  
> hostconfig).

Have you read hostconfig???

There's a lot more it defines than hostname. It defines global  
variables that are use by SystemStartup items and many other things.

Also hostname set like that won't stick, and can change even while  
the system is booted, because it's just plain the wrong way to set it.


-dhan

------------------------------------------------------------------------
Dan Shoop <shoop at iwiring.net>
Tactical Operations Center: 1.866.901.8787 (24x7)
Ph: 714.363.1174
AIM: iWiring