On Fri, 2009-01-23 at 14:33 +0000, Konstantin V. Gavrilenko wrote: > -------- Original Message -------- > Subject: Re: [fprint] dbus + fprintd error > From: Bastien Nocera <[email protected]> > To: [email protected] > Cc: [email protected] > Date: 23/01/09 11:37 > > <SNIP> > >> Another issue, I though that fprintd was suppose to allow simultaneous > >> non interlocking access to the fingerprint device by several > >> processes. > >> However, if i run one instance of su - and another one in the second > >> terminal, the second goes straight into Password prompt. > >> > >> Was I wrong in assuming that it can be used by several processes > >> simultaneously? > > > > Yes and no. Both programs were waiting on a read on the fingerprint > > reader. They are "interlocking", only one process can access the device > > at a time... > > > > Cheers > > > > Ok. Just a suggestion. Instead of skipping the fingerprint authentication > and going to the second defined method (password). > I think it is a good idea to include a notification that fingerprinting > device is busy, so unable to proceed with fingerprint login and either
You can't do the "either" using PAM. So we used the latter method and skipped to password authentication. > wait > until the device gets free, or skip the step and authenticate using the > second pam defined method. > > > > _______________________________________________ fprint mailing list [email protected] http://lists.reactivated.net/mailman/listinfo/fprint
