Date: Tue, 28 May 2024 16:05:15 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 279365] Incomplete syslog message on console after login timeout Message-ID: <bug-279365-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D279365 Bug ID: 279365 Summary: Incomplete syslog message on console after login timeout Product: Base System Version: 15.0-CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: bugs@FreeBSD.org Reporter: jfc@mit.edu When login on the console times out an apparent race between respawning get= ty and logging the failure results in an incomplete syslog message on the cons= ole. This is the console: FreeBSD/arm64 (striatus) (ttyu0) login: invalid Password: Login incorrect login: Login timed out after 300 seconds May 28 10:56:38 striatus login[66089] FreeBSD/arm64 (striatus) (ttyu0) login:=20 The full message is in /var/log/messages: May 28 10:56:38 striatus login[66089]: 1 LOGIN FAILURE ON ttyu0 Possibly getty is interrupting a non-atomic write by syslog. I know syslog= is capable of reporting the full message because I see it if I type ^D instead= of waiting for login to give up. This is my console device: uart0: <PrimeCell UART (PL011)> mem 0xe1010000-0xe1010fff irq 13 on simpleb= us0 uart0: console (115200,n,8,1) Externally it appears as a type B USB socket, device ID 2e02:1000 (SoftIron OverDrive 1000), version 1.02, full speed. It is plugged into a Mac. --=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-279365-227>