On 10/18/2011 09:03 AM, Ludovic Rousseau wrote:
The [Install] section is used when someone runs 'systemctl enable' /
'systemctl disable' on the pcscd.service file. When a user runs the
command, the WantedBy=multi-user.target line adds the pcscd.service
dependency to the multi-user.target, effectively marking pcscd to always
start up on system boot. I can imagine that some people would want to do
that, but I'm personally fine with killing that use case.
OK. I will remove it.
The only reason I find to start pcscd at boot is because pcscd is slow
to start. This can happen if you have _a lot_ of USB readers or slow
to setup readers like serial ones.
Ludovic, I've been busy for some time and not reading the list... so
this mail comes late I fear.
I engineered an appliance which has sold more than 50 parts in Italy,
mainly to local authorities; I think this is the kind of successful
product you can be proud of -meaning: of course, it uses pcscd!
There is a _VERY_ high number of smart cards conncted to that (actually
I changed the code for supporting more than 16 readers) and I start
pcscd at boot because operations must begin at boot-time; I think that
allowing the daemon to be switched on when I need is definitely required
here (and even stopping it, even if at the moment I do not see a reason
why).
Also, when attaching many smart cards, I want to be sure to perform
scanning when they are all connected and seen by the USB/system, meaning
pcscd should be already on or, alternatively, off until I'm sure that
all the USB have settled, then I switch it on.
Am I keeping control over this, or by what I understand I'm going to
miss the opportunity to launch/stop pcscd? I'm worried...
Is the idea to start pcscd when a smart card reader is connected?
Why do you want that?
_______________________________________________
Muscle mailing list
[email protected]
http://lists.drizzle.com/mailman/listinfo/muscle
