My project has nothing at all to do with security or smart cards,
yet, somehow, pcscd is launched because of a custom piece of hardware
and then my communication with this piece of hardware causes pcscd to
spike CPU consumption and never go away (and it cannot be killed,
and, even better, running anything that attempts to query the run-
away pcscd process, e.g. ps / top/ etc., hangs).
This project (which I only recently took control of) pre-dates 10.4
and this problems seems to have started since the arrival 10.4 (one
user blames 10.4.3), however, I don't have much historical
perspective on this issue. Here is what I do know, the custom piece
of hardware is an array of 11 digital cameras connected to (from my
perspective) a "black box" controller for the cameras. This
controller connects to a Mac via USB, and my application talks to
this camera controller via a driver which is compiled as a bundle
package and located inside of my app's app package.
Problem #1: When this USB-based peripheral is plugged into a Mac
pcscd is launched. Why? Is there some debug flags I can set to find
out what securityd is thinking which causes it to launch pcscd?
(which, I've read, is the protocol for its launch)
Probelm #2: My code communicates with the USB-device and pcscd
freaks out.
My thinking is that if I can figure out #1 then #2 becomes irrelevant
because none of this security stuff should ever be involved with
either this peripheral nor its associated software. However, problem
#1 has nothing to do with any of my software since plugging in the
device brings pcscd into the mix without any interaction with my code
(it is not running).
ANY help would be greatly appreciated.
Mark Sanvitale
Electrical Geodesics, Inc.
email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Apple-cdsa mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/apple-cdsa/email@hidden