help! pam.d and pam_tally setting mess up xscreensaver login!!!!

[Tomas Mraz]

On Thu, 2006-02-02 at 17:42 -0800, Christian Seberino wrote:
> Why Debian has this problem but not Fedora?  The permissions
> for /var/log/faillog look the same for both.  Does Fedora
> do some setuid magic or something dangerous to "fix" the xscreensaver?
The default is onerr=succeed. And fedora doesn't use pam_tally at all by
default.

> Chris
> 
> 
> On Tue, 2006-01-31 at 09:53 +0100, Tomas Mraz wrote:
> > On Mon, 2006-01-30 at 16:01 -0800, Christian Seberino wrote:
> > > How come if I uncomment pam_tally line in common-auth file below (Debian
> > > box) I cannot unlock the screensaver with a password anymore?
> > Put there onerr=succeed instead of onerr=fail. xscreensaver in debian
> > cannot access the /var/log/faillog file and thus the pam_tally module
> > fails with error.
> > 
> 
-- 
Tomas Mraz <tmraz at redhat.com>