Am 29.07.2014 14:43, schrieb Karel Zak: > systemd TODO: > > - Replace utmp, wtmp, btmp, and lastlog completely with journal > > Can someone elaborate and provide more details, ideas, .. ? > > The current lastlog is sparse file and it's difficult to use for backup > programs or integrity checkers, etc. So requests from users/customers > are pretty common. > > The idea (from someone from RH) is to have very simple and tiny > library that provides unified API for different backends (classic > lastlog, systemd journal, etc.) to keep applications portable. > Something like: > > https://github.com/marmolak/liblastlog2 > > Frankly, I'd like to see something more than only lastlog, but also > utmp, wtmp support. > > Note that I'm not involved in the project, but as login(1), last(1), > ... maintainer I'd like to see a public discussion about this topic. > > > Maybe all we need for things like lastlog and wtmp is journald and then > a few #ifdef in applications like login(1), who(1) or PAM. Maybe it > would be better than add an extra abstraction layer (by any library). > Not sure, too many question :-)
please keep in mind that on servers "Storage=volatile" and forward to classic rsyslog is common and that won't change - so whatever you read from journal are only recent entries which won't survive a reboot additionally use journald in such setups means you get that all to rsyslog forwarded and with no caution taken it will land in /var/log/messages
signature.asc
Description: OpenPGP digital signature
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
