Hi, I know there are problems with the coolkey package on RHEL 5
On linux, also verify that you have no java process trying to use javax.smartcardio connections running. This conflicts whith native applications also using pcsclite. Regards Sebastien On Tue, Mar 23, 2010 at 11:54 AM, <[email protected]> wrote: > I use SCARD_SHARE_EXCLUSIVE mode. > On the desktops, there are more and more apps trying to use SmartCards... > Did you try to insert a Card with windows seven for example ... it really > tries to install a driver for the card the same way of a new peripheral ! > > I'm sure there will be more and more SHARE card problems in a future (that > I however hope to be soon) ... > > regards, > > Gui > > ----- Mail Original ----- > De: "Ludovic Rousseau" <[email protected]> > À: "MUSCLE" <[email protected]> > Envoyé: Mardi 23 Mars 2010 11h19:24 GMT +01:00 Amsterdam / Berlin / Berne / > Rome / Stockholm / Vienne > Objet: Re: [Muscle] SCARD_E_SHARING_VIOLATION information > > 2010/3/23 <[email protected]>: > > 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 your application is the only one using PC/SC you should not have > any problems (except your owns). > > Do you use SCardConnect in SCARD_SHARE_SHARED or SCARD_SHARE_EXCLUSIVE > mode? > > > If there is no official way, would it mean that such a thing could > however be developed inside PCSC, or at the kernel level ? > > pcsc-lite does not store the id of the processes using the readers. So > anything is possible but development is needed. > Have you looked at the pcscd logs? > > > 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 ? > > I forwarded your request to David Corcoran, maintainer of the web site. > > 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 >
_______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle
