Yep, I agree. For this reason, I think an easy way to identify conflicting applications will be usefull. Isn't PCSCD the key-stone for this ? Gui
----- Mail Original ----- De: "Martin Paljak" <[email protected]> À: "MUSCLE" <[email protected]> Envoyé: Mardi 23 Mars 2010 12h31:20 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne Objet: Re: [Muscle] SCARD_E_SHARING_VIOLATION information On Mar 23, 2010, at 13:01 , Sébastien Lorquet wrote: > > 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. It requires that all the applications accessing smart cards are either a) configured/designed for exclusive access and by administrative means guaranteed to really be the only application accessing the card reader b) designed to work in a shared environment and designed to share the reader. Mixing two styles causes problems. Unfortunately different applications are written by different folks who consider only one configuration the "Right Way Under All Conditions". -- Martin Paljak http://martin.paljak.pri.ee +3725156495 _______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle _______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle
