[launchd-dev] launchd-dev Digest, Vol 24, Issue 5

[Nehemiah Dacres]

Not to dissagree with the engeneer, but this falls out of LaunchD domain and
in the domain of IOKit. Whats to stop the driver programmer
from implementing this level of granularity? What does the origenal poster
mean by "Interaction"?

On Fri, Jun 5, 2009 at 9:00 AM, <launchd-dev-request at lists.macosforge.org>wrote:

> Send launchd-dev mailing list submissions to
>        launchd-dev at lists.macosforge.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>        http://lists.macosforge.org/mailman/listinfo.cgi/launchd-dev
> or, via email, send a message with subject or body 'help' to
>        launchd-dev-request at lists.macosforge.org
>
> You can reach the person managing the list at
>        launchd-dev-owner at lists.macosforge.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of launchd-dev digest..."
>
>
> Today's Topics:
>
>   1. Re: Launch daemon 0n-Demand on USB Connection/Write
>      (Damien Sorresso)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 04 Jun 2009 17:00:11 -0700
> From: Damien Sorresso <dsorresso at apple.com>
> To: Kiran B <Kiran.b at robosoftin.com>
> Cc: launchd-dev at lists.macosforge.org
> Subject: Re: [launchd-dev] Launch daemon 0n-Demand on USB
>        Connection/Write
> Message-ID: <BF826895-D2AB-4AFD-A763-898CDB189165 at apple.com>
> Content-Type: text/plain; charset="us-ascii"; Format="flowed";
>        DelSp="yes"
>
> On Jun 3, 2009, at 12:45 AM, Kiran B wrote:
> > Hello,
> >
> > From the recent posts in "launchd-dev" lists, it is evident that
> > launchd does not yet support launching of processes based on USB
> > device getting connected.
> >
> > I have a requirement to launch a daemon whenever a device with
> > specific VendorID is connected.
> >
> > I am OK even if the daemon gets launched for any device getting
> > connected via USB. In that case, the daemon shall ensure that it is
> > the right device on which it is interested in. In other case it may
> > terminate.
>
> For now, you should have a monitor daemon that keeps track of what's
> happening with IOKit. When the device you want appears, it asserts
> demand for your other daemon by sending a message to a Mach port or
> connecting to a socket. Then your other daemon gets launched on demand.
>
> > I am also curious to know whether a daemon can be launched whenever
> > the connected device writes any data on the USB port. (Eg: User
> > interaction with the device would make the device write on USB).
>
> No. If we do implement hardware event-based notifications, it wouldn't
> be quite this granular.
> --
> Damien Sorresso
> BSD Engineering
> Apple Inc.
>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: smime.p7s
> Type: application/pkcs7-signature
> Size: 2425 bytes
> Desc: not available
> URL: <
> http://lists.macosforge.org/pipermail/launchd-dev/attachments/20090604/b5916d53/attachment-0001.bin
> >
>
> ------------------------------
>
> _______________________________________________
> launchd-dev mailing list
> launchd-dev at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/launchd-dev
>
>
> End of launchd-dev Digest, Vol 24, Issue 5
> ******************************************
>



-- 

"lalalalala! it's not broken because I can use it"

http://linux.slashdot.org/comments.pl?sid=194281&threshold=1&commentsort=0&mode=thread&cid=15927703
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/launchd-dev/attachments/20090606/fce65c51/attachment.html>