Date: Sun, 15 Jul 2018 07:38:21 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 229775] syslog(3) includes process id in each message even if LOG_PID is not specified as 2nd argument of openlog(3) Message-ID: <bug-229775-227-t8MaAbOaLf@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-229775-227@https.bugs.freebsd.org/bugzilla/> References: <bug-229775-227@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=3D229775 --- Comment #3 from Yasuhiro KIMURA <yasu@utahime.org> --- (In reply to Yuri Pankov from comment #2) Behavior on 12-CURRENT doesn't conform to POSIX standard and breaks compatibility with other UNIX-like OSes. And it results in change of application behavior not intended by author. One example is security/sudo. According to man page of sudoers(5) there is following configuration option. ---------------------------------------------------------------------- syslog_pid When logging via syslog(3), include the process ID in the log entry. This flag is off by default. ---------------------------------------------------------------------- On 11.2-RELEASE it works as is expected. But on 12-CURRENT it doesn't becau= se process ID is included regardless of this option. And from the viewpoint of user it looks like bug of sudo. So it is possible someone reports it to aut= hor of sudo. Then he will investigate and find behavior of syslog(3) changed on 12-CURRENT. And to make matters worse he will also find there is no way to implement it correctly. So it is quite possible he blames syslog(3) of 12-CURRENT is broken. --=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-229775-227-t8MaAbOaLf>