https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229775
--- Comment #4 from Ed Schouten <[email protected]> --- 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 entries 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 behind 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 name, etc.), even if no flag were to be set. Though I agree that the new syslog(3) implementation is unconventional in that 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. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "[email protected]"
