Comment # 3 on bug 1228378 from Christian Boltz

(In reply to Thorsten Kukuk from comment #2)
> You mixed up lastlog2 with wtmpdb. Lastlog2 is the successor of lastlog,
> while wtmpdb is the replacement for /var/log/wtmp

Right (and thanks for pointing it out!), but since I'm only interested in the
last login, lastlog2 loooked like a better fit.

In the meantime, I found out that parsing the output of lastlog2 is harder than
I thought - despite including the timezone ("+0200"), the result (converted to
unixtime) depends on $TZ :-(

That makes reading directly from /var/lib/lastlog/lastlog2.db looking more
interesting and easy. The obvious disadvantage is that it would mean to use the
back door instead of the official (but harder to use) front door tools.

Is the database layout of /var/lib/lastlog/lastlog2.db expected to be quite
stable, or is it a terrible idea to directly access it?