I'm working with SAM, connected to a critical server with critical application. It may happen, someday (or even night), that the application cannot connect to a SAM because of SHARING_VIOLATION ... I hope that this will never happen, but in such a situation, we must record a maximum of log information that will allow to determine the reason of the SHARING_VIOLATION, and find the guilty process to definitively solve the issue. On a desktop for example, I encountered this problem. After investigation it was a RedHat Gnome applet's fault that try to identify the inserted cards.
If there is no official way, would it mean that such a thing could however be developed inside PCSC, or at the kernel level ? By the way : "http://www.linuxnet.com/musclecard/index.html"; indicates a broken link to "The following article describes the MuscleCard architecture and it's components" Can any one fix it ? Regards, Gui ----- Mail Original ----- De: "Ludovic Rousseau" <[email protected]> À: "MUSCLE" <[email protected]> Envoyé: Mardi 23 Mars 2010 09h07:03 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne Objet: Re: [Muscle] SCARD_E_SHARING_VIOLATION information 2010/3/22 <[email protected]>: > I would like to know if there is any way for obtaining more information when > encountering a SCARD_E_SHARING_VIOLATION during a SCardConnect() ? > In a different spelling : when I get SCARD_E_SHARING_VIOLATION during a > SCardConnect(), I would like to have information concerning the process that > has already obtained exclusive rights (its PID for example). This service is not available from the winscard API. So there is no official way to retrieve the information you want. > Do you have any trick ? You can have a list of _all_ the processes using the PC/SC API using: $ sudo fuser /var/run/pcscd/pcscd.pub Why do you need this? Bye -- Dr. Ludovic Rousseau _______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle _______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle
