Re: Replacing launchd
Re: Replacing launchd
- Subject: Re: Replacing launchd
- From: James Berry <email@hidden>
- Date: Fri, 30 Sep 2005 12:01:30 -0700
On Sep 30, 2005, at 11:39 AM, Graham J Lee wrote:
Dave Zarzycki wrote:
Today, launchd's operating goal is to find *any* reason to run a
job and run it.
launchd tries hard to stay out of the business of providing
policy mechanisms like this for multiple reasons:
[...]
For all of these reasons, I don't see limits like this being added
to launchd any time soon.
Oh well, I scratched my itch, learned stuff about the way OS X
works in the process, and modified the behaviour of my system to
better suit my usage. So I'm happy :-)
As Peter Seebach wrote, perhaps a separate policy wrapper -
analogous to tcpd for network services - is the way that should
"really" go. Oh dear, I'm already considering firing up Xcode
again... ;-)
You might look at daemondo (of which I'm the author) which is part of
the darwinports code (cvs HEAD). Its purpose is to function as an
intermediary between launchd and your daemon of choice. It already
links against SystemConfiguration, and friends in order to provide
various processing for network and power states. You might look at
extending this to provide anything additional you need. It knows how
to execute various commands in response to various stimuli.
Cheers,
Graham.
_______________________________________________
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
_______________________________________________
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