Re: StartupItems
Re: StartupItems
- Subject: Re: StartupItems
- From: "Jordan K. Hubbard" <email@hidden>
- Date: Mon, 15 May 2006 12:59:00 -0700
On May 15, 2006, at 12:00 PM, Finlay Dobbie wrote: That's much more efficient than starting a service and vending a name hoping someone wants to use it, or wants to wait for it.
Depends. In a server environment, I'd want the service available and ready to take client connections immediately - without any startup overhead - especially if it needs to perform lengthy initialisation.
You can't generalize like that, however. You might want SOME services to start immediately (in which case, the RunAtLoad launchd plist item is probably your friend) but ALL services? No way. That's just wasteful, and unless you make a habit of putting 4GB (for now!) of memory in every machine you own, probably going to have a noticeable performance impact as other things fight for the memory that's being taken up by all those services just lying around doing their nails and watching daytime TV.
Sorry, but the "server environment" classification hardly guarantees that each and every service being provided by the server needs to be running all the time, particularly in SOHO configurations where one box serves potentially dozens of needs "in theory" but, in practice, finds many of those needs to be occasional usage scenarios at best.
- Jordan
|
_______________________________________________
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