From owner-freebsd-bugs@freebsd.org Wed Jun 5 17:50:14 2019 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 B4BA515B4593 for ; Wed, 5 Jun 2019 17:50:14 +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 3787F8C906 for ; Wed, 5 Jun 2019 17:50:14 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id EC24515B4592; Wed, 5 Jun 2019 17:50:13 +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 C4F7815B4591 for ; Wed, 5 Jun 2019 17:50:13 +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.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 58EC78C903 for ; Wed, 5 Jun 2019 17:50:13 +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 7FCD8D0FE for ; Wed, 5 Jun 2019 17:50:12 +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 x55HoCkL029064 for ; Wed, 5 Jun 2019 17:50:12 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x55HoCBT029063 for bugs@FreeBSD.org; Wed, 5 Jun 2019 17:50:12 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 238345] usr/bin/logger: Old syslog format when using remote host option (-h) Date: Wed, 05 Jun 2019 17:50:12 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new 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: zeising@FreeBSD.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: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: 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.29 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jun 2019 17:50:14 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D238345 Bug ID: 238345 Summary: usr/bin/logger: Old syslog format when using remote host option (-h) Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: bugs@FreeBSD.org Reporter: zeising@FreeBSD.org About a year ago, syslogd(8) and subsequently syslog(3) grew the feature to handle rfc5424 syslog formats. logger(1) is a small CLI interface to syslog(3), with which you can generate log messages to either log locally, = or remotely. When using logger without the -h option, it uses the syslog(3) libc interfa= ce to format and send a log message to the default place, usually a socket /var/run/log, on which syslogd(8) listens. Since syslog(3) generates rfc54= 24 compliant messages, this will also be rfc5424 compliant. When using logger with the -h option, to send logs to another machine, or another local socket, logger(1) formats the message in a non-rfc5424 compl= iant manner. This causes a lot of confusion, since the behavior is quite differ= ent depending on whether -h is used or not. I would like to see that logger(8) grew the ability to generate rfc5424 messages in all cases, but I'm unsure about how to proceed. One idea is to simply take the code from syslog(3) (really vsyslog1()) which generates rfc= 5424 compliant messages, and put that in logger(1). Another idea is to make the rfc5424 message generator a function in either libc or another library, for both syslog(3) and logger(1) (and possibly others) to consume. Which way is best? Thanks! --=20 You are receiving this mail because: You are the assignee for the bug.=