[Buildroot] Dropbear reports errors in system log
Will Moore
will.moore at beraninstruments.com
Mon Sep 12 11:39:51 UTC 2011
Buildroot dropbear is configured to log ssh access to /var/log/lastlog and
/var/log/wtmp as well as /var/log/utmp. It successfully logs to /var/log/utmp
but reports the following entries in the /var/log/messages system log:
Sep 12 06:42:43 buildroot authpriv.warn dropbear[1019]: lastlog_perform_login:
Couldn't stat /var/log/lastlog: No such file or directory
Sep 12 06:42:43 buildroot authpriv.warn dropbear[1019]: lastlog_openseek:
/var/log/lastlog is not a file or directory!
Sep 12 06:42:43 buildroot authpriv.warn dropbear[1019]: wtmp_write: problem
writing /var/log/wtmp: No such file or directory
I believe these errors can be stopped either by creating /var/log/lastlog and
/var/log/wtmp (but this would seem to just duplicate logging) or by configuring
dropbear --disable-lastlog and --disable-wtmp (better). Is there something I am
missing?
I note that other login accesses are reported to /var/log/utmp too. Is there
anything stopping /var/log/utmp growing over time?
Regards,
Will
More information about the buildroot
mailing list