From: Anthony F. <ant...@gm...> - 2013-05-31 23:33:00
|
Florent -- On Fri, May 31, 2013 at 12:53 AM, Florent Deybach <fde...@gm...> wrote: > Hi, > > Thanks for answer! > > >> If you are talking about pcscd starting automatically when the system >> boots, then that is a question for your system init framework. I >> believe that Ubuntu uses "upstart": >> >> >> http://upstart.ubuntu.com/cookbook/#disabling-a-job-from-automatically-starting > > > No, I am talking about the pcscd daemon starting when libpcsclite starts the > communication. Hm. I looked around for a while, seeing where this was done, only to see this: http://anonscm.debian.org/viewvc/pcsclite?view=revision&revision=6105 $ svn log -r 6105 ------------------------------------------------------------------------ r6105 | rousseau | 2011-11-14 03:19:44 -0700 (Mon, 14 Nov 2011) | 8 lines Remove pcscd autostart feature The auto start feature (launch pcscd from the library if not already running) was a fragile code with some issues. This service is far better implemented by systemd. Thanks to Kalev Lember for pushing the systemd patches. So if your libpcsclite is still spawning pcscd, then it's relatively old. Further, it sounds like the logic for this is now run by systemd, which means that (since you're using upstart) you'll either need to contribute bits that provide the same support, or find a way to have your upstart install provide this feature. (As far as I understand it, systemd can act a bit like inetd / xinetd; it "knows" about a socket (and hence creates it), but it doesn't launch the actual daemon until someone tries to connect to it.) However, if your distro has upstart and pcscd playing nice together already, then you can probably disable the pcscd socket through the upstart config mechanisms. If I'm wrong on that, someone please correct me -- this isn't something I've worked on in detail. Either way, good luck to you, Florent. Best regards, Anthony Foiani |