Date: Mon, 06 Feb 2017 15:17:03 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 209441] SSHd in FreeBSD 10.3 complains about PrintLastLog Message-ID: <bug-209441-8-WBFvdCdcSN@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-209441-8@https.bugs.freebsd.org/bugzilla/> References: <bug-209441-8@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D209441 Dag-Erling Sm=C3=83=C2=B8rgrav <des@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Open Assignee|freebsd-bugs@FreeBSD.org |des@FreeBSD.org --- Comment #8 from Dag-Erling Sm=C3=83=C2=B8rgrav <des@FreeBSD.org> --- Miroslav: the problem is (or was, at the time) that the configure script lo= oks for the actual log files rather than the APIs. If you try to build OpenSSH= on a machine that was upgraded from an older FreeBSD version and still has old= log files lying around, the configure script will enable lastlog and the build = will fail. Conversely, it may incorrectly disable lastlog on a system that supp= orts it if you try to configure and build in a pristine chroot or jail (like poudriere does), because the log files aren't created until someone logs in. Steven: the bug is not that PrintLastLog doesn't work. It *can't* work, bec= ause FreeBSD doesn't have that API any more. The bug is that it is still documen= ted. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-209441-8-WBFvdCdcSN>