hostconfig process
LuKreme
kremels at kreme.com
Thu Aug 16 22:58:54 PDT 2007
On Aug 16, 2007, at 3:21 PM, R.L. Grigg wrote:
>> If indeed efficiency of time was of value to you, you might find
>> that reading about how things operate, even if just that section
>> of a book or a man page, might well reward itself and payoff with
>> interest compared to time spent chasing unrewarding
>> misconceptions. That is to say it's the lazy man that reads once,
>> and then thinks correctly.
>
> Translation: Dan doesn't know the answer, and couldn't/wouldn't
> articulate it even if he did know.
Many things Dan may be, but misinformed on this topic is not one of
them.
You are seeing a change in hostconfig and assuming that this change
causes your service to launch. this is not true. Even at boot, all
this line does is allow the process to be launched by its agent
(whatever agent that might be as define, if you read the man pages,
by the appropriate plist). This is an important distinction.
Where I not 3000km from home, I'd have more to say on this, but I can
say that if you don't understand how launchd works, you are going to
almost certainly get yourself into a barrel of trouble rushing over a
rather high water fall.
man launchd is not that complicated and points you the files that are
important (under FILES) and the other related commands to look at
(under SEE ALSO).
Lambasting Dan, as fun as that may be, is not going to help you
understand what your problem was and/or is and will not do anything
at all to help you in the future. Read the man pages.
More information about the MacOSX-admin
mailing list