Re: StartupItems
Re: StartupItems
- Subject: Re: StartupItems
- From: Graham J Lee <email@hidden>
- Date: Tue, 23 May 2006 10:07:31 +0100
On 23/5/06 07:33, Peter Seebach wrote:
In message <email@hidden>, Michael Smith wr
ites:
Change is pain, and you really have just two choices; impede the
process and contribute nothing, or align yourself with it and help
these folks improve the world a little.
I've suggested the obvious improvement: Stop trying to crowbar system
startup into launchd. Use it for on-demand services and other things that
can be started "once the system is up".
I think the argument would be that system startup is just a specific
example of the general case "something interesting happened and I want
to be run because of it", and that launchd deals with the happening of
interesting things. I'd agree with that, if it were the argument :-)
As a sysadmin, launchd's allowed me to consolidate a mess of crontabs,
inetd/xinetd configurations, watchdog configurations[1], StartupItems
and custom rc.local files into a mess of plists looked at by just two
tools[2]. Still speaking as a sysadmin I tend to think of programs that
aren't launchd-ready as being so last century (what with there probably
being an order of magnitude more Tiger users than any other Unix
distribution, apart from maybe panther) and in need of some updating.
Of course, my dev hat reminds me how much work that can involve...
Cheers,
Graham.
[1]which joker decided that they wanted *both* types of init?
[2]launchd, and an arbiter tool to take care of things like TCP
wrappering and so on.
--
Graham Lee
UNIX Systems Manager,
Oxford Physics Practical Course
http://users.ox.ac.uk/~wadh1342
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden