Date: Sun, 15 Jul 2018 13:43:34 +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-Gu7JdlR0Mo@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 #4 from Ed Schouten <ed@FreeBSD.org> --- Hi Kimura-san, This change was made for the reason that many applications fail to set this flag even though they should, meaning that it's hard to distinguish log ent= ries for multiple worker processes, detect process restarts, etc. The claim that this breaks conformance with POSIX is in my opinion unsubstantiated. Even though POSIX defines the API and explains the idea be= hind flags like LOG_PID, it in no way describes the actual process of logging or= the exact format that is used to store entries on disk. We're allowed to log any additional metadata we want (unique message IDs, user IDs, associated TTY n= ame, etc.), even if no flag were to be set.=20 Though I agree that the new syslog(3) implementation is unconventional in t= hat sense, I think that this change should be seen as something positive. It improves traceability. I therefore suggest that we close this with WONTFIX = if others agree. --=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-Gu7JdlR0Mo>