hostconfig process

[R.L. Grigg]

On Aug 14, 2007, at 9:46 PM, Justin C. Walker wrote:
>
> On Aug 14, 2007, at 16:43 , R.L. Grigg wrote:
>
>> On Aug 10, 2007, at 4:06 PM, Justin C. Walker wrote:
>>>
>>> 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.
>>
>> For example in Sys Prefs under Sharing when you select to enable  
>> Apple Remote Desktop it modifies the settings in /etc/hostconfig:
>>    ARDAGENT=-YES-
>> and then somehow enables it without a reboot. I assume by  
>> restarting some process. Just wondering which one? Or is there a  
>> simpler way to do this.
>
> Are you getting a clearer picture of what is going on?  If you are  
> just interested in ARDAGENT, Dan gave you the answer, I think.  For  
> the general case, it's a bit too twisty to nail down and be able to  
> bank on across releases: if it's "/etc/hostconfig" you want to  
> modify, reboot is in order.  If you are after a specific item  
> therein, there may be an answer that does not require reboot (but  
> that could change the next time the OS changes).
>

Yes thanks I'm just trying to bridge the gap between theory and reality.

For the ARDAGENT case, it seems that ARDHelper parses the hostconfig  
file for the ARDAGENT=-YES- line, and if -YES- launches ARDAgent.

For the sshd case, its launch is based on the .plist, but I'm still  
overlooking something:
     % sudo launchctl load -w /System/Library/LaunchDaemons/ssh.plist
     Workaround Bonjour: Unknown error: 0

Thanks
Russ