Hello, On Sat, Sep 4, 2010 at 21:29, Peter Stuge <pe...@stuge.se> wrote: > Martin Paljak wrote: >> >> Why not make the udev rule start pcscd, >> > >> > One reason is that it needs highly distribution dependent udev rules, >> >> Existence of pcscd group is also distribution dependent, to some >> extent (meaning, it has to exist and maybe needs to be created) > > True. This is typically dealt with by the package however, which is > by definition already distribution specific. :)
The same way patching the udev file is done by the package (creator), as needed. >> How many distributions don't put pcscd to /usr/sbin? > > That's not the full story. System pcscd would be a service, and how > to start a service varies from distribution to another: > > /etc/init.d/pcscd start > start pcscd > systemctl start pcscd.service > svc -u /service/pcscd With all due respect (I'm sure theres a huge list of "good old Unix practices" I might break), a service (like Apache, some SQL server, mail service) is not the same as a daemon process (anything that forks to the background and has has a name ending with a d). IMHO it does not matter how the pcscd process gets execve()-d, and pcscd already blurs the line with the auto-start by user API calls. Nothing bad will happen if pcscd is not gracefully shut down when the computer is rebooting, which is not true for a mail server or SQL server. The "system daemon conventions" are only there to wrap execve to something that makes sure all "services" look the same. But there's no /etc/init.d/gconfd for example. _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
