Date: Sun, 10 May 2026 07:15:07 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 295171] syslogd logs confusing messages when trying to log to non-existing ttys Message-ID: <bug-295171-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=295171 Bug ID: 295171 Summary: syslogd logs confusing messages when trying to log to non-existing ttys Product: Base System Version: 14.4-STABLE Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: bin Assignee: bugs@FreeBSD.org Reporter: mail@fbsd2.e4m.org Created attachment 270560 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=270560&action=edit patch When one of my NVMEs became to warm, smartd logged this fact using a priority which triggered syslogd to inform me via a message on the tty: May 10 07:25:15 <daemon.crit> voyager smartd[2431]: Device: /dev/nvme0, Temperature 41 Celsius reached critical limit of 40 Celsius (Min/Max 16/47) Additionally, this message appears each time: May 10 07:25:15 voyager syslogd: /dev/:0: No such file or directory This is because syslogd walks through getutxent() entries and finds one where ut_line is set to ":0" (which probably comes from my logon through xdm). A possible fix might be to check if ut_line contains a colon (and silently ignore it in this case), see patch. Another option would be not to complain in ttymsg_check() when stat()ing the tty failes (and return NULL) as ttystat() does it in w(1). -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-295171-227>