2010/2/5 Dominik <dom_fisc...@web.de>: > If pcscd should handle PCMCIA-based SmartcardReader it is necessary that > pcmcia is ready and has found all devices before pcscd is started. After > Start of pcscd it needs some time to initialize itself (finding all > smartcardreaders, etc.).
PCMCIA readers can be hotpluged. When the reader is plugged or unplugged just execute "pcscd --hotplug". I guess a udev rule can do that. No need to wait after PCMCIA is setup. > Other resources like GDM (Smartcard-based login) and NetworkManager > (Smartcard-based VPN) should wait for pcscd to be ready (if it is > installed)! They should wait for pcscd to _start_, not be _ready_. If pcscd is started but not ready yet the application using it will be blocked in SCardEstablishContext() until pcscd is readry to answer. > As a starting point I've written an upstart init script (attached). > This script emits a signal after pcscd has been started and settled down > (sleep 5). I know this is ugly, but as stated before simply starting > pcscd -- and after that the NetworkManager/GDM -- can lead to a kind of > "race condition". > > I've also changed the upstart init script for NetworkManager and GDM to > wait for the emited signal. The next version of pcscd will not be started at startup but when an application needs it. You can already play with the beta at [1]. What is still missing is the udev rule to correctly set the access rights to the readers. Bye [1] http://ludovic.rousseau.free.fr/softwares/pcsc-lite/ -- Dr. Ludovic Rousseau -- Upstart job for pcscd https://bugs.launchpad.net/bugs/506908 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
