From owner-freebsd-bugs@freebsd.org Sun Jul 15 07:38:23 2018 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6B4CE102E79C for ; Sun, 15 Jul 2018 07:38:23 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 049AE7C61F for ; Sun, 15 Jul 2018 07:38:23 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id BA0D7102E79B; Sun, 15 Jul 2018 07:38:22 +0000 (UTC) Delivered-To: bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A75F5102E79A for ; Sun, 15 Jul 2018 07:38:22 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2E1F87C61A for ; Sun, 15 Jul 2018 07:38:22 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 5E87522B8D for ; Sun, 15 Jul 2018 07:38:21 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w6F7cLUV014477 for ; Sun, 15 Jul 2018 07:38:21 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w6F7cL67014474 for bugs@FreeBSD.org; Sun, 15 Jul 2018 07:38:21 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f 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) Date: Sun, 15 Jul 2018 07:38:21 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: yasu@utahime.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Jul 2018 07:38:23 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229775 --- Comment #3 from Yasuhiro KIMURA --- (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.=