[Pkg-shadow-devel] Bug#603234: Bug#603234: [login] lastlog's login dates older than actual last login dates

Nicolas François nicolas.francois at centraliens.net
Fri Nov 19 22:31:13 UTC 2010


On Tue, Nov 16, 2010 at 11:56:24PM -0500, chealer at gmail.com wrote:
>  On 2010-11-16 18:11, Nicolas François wrote:
> >>its login dates are just older than actual
> >>last login dates. There is also no single login program that I use.
> >>I use at least kdm (KDE) to login to X :0 and su to login as root
> >>(from konsole).
> >[...]
> >>So lastlog didn't change since 10 days.
> >Can you check if this is fixed by setting UseSessReg in kdm.options,
> Is UseSessReg documented anywhere? Here is the content of kdm.options:

I'm not using kdm. I've not checked. I just saw UseSessReg mentionned on
google (maybe with an old version of kdm).

My guess is that UseSessReg executes sessreg, which has a manpage.

> >this can be fixed by adding this line to the PAM configuration file of
> >kdm:
> >session  required  pam_lastlog.so silent
> "This" cannot be fixed this way, but lastlog does become aware of
> logins through kdm after adding that line.

I fail to understand the above line.
"fixed" and "lastlog does become aware of logins" looks identical in your
use case.

> >You will also have to reassign this bug to kdm
> >
> This bug is about more than kdm, and I have no ground to argue that
> kdm is at fault here, unless I'm missing some part of policy.

What is at fault in the login package?
lastlog is only a tool which permits to display the entries from

If you think kdm should report to /var/log/lastlog, you should file a bug
for kdm.
If you think this should not be the default because it is specific to your
configuration, then change you kdm PAM configuration.

It might also be done in /etc/pam.d/common-session in order to register
all interactive logins. This will have to be synchronized with all the
services which use common-session in order to avoid duplicates.


More information about the Pkg-shadow-devel mailing list