From owner-freebsd-hackers@freebsd.org Sun Sep 30 10:17:06 2018 Return-Path: Delivered-To: freebsd-hackers@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 3C26510BB38C for ; Sun, 30 Sep 2018 10:17:06 +0000 (UTC) (envelope-from timp87@gmail.com) Received: from mail-wm1-x32f.google.com (mail-wm1-x32f.google.com [IPv6:2a00:1450:4864:20::32f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9BE4A7CBF0 for ; Sun, 30 Sep 2018 10:17:05 +0000 (UTC) (envelope-from timp87@gmail.com) Received: by mail-wm1-x32f.google.com with SMTP id o18-v6so5922044wmc.0 for ; Sun, 30 Sep 2018 03:17:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=wIf5HJMGnBBFp/6vv4Yo7cE7SjGz9jbwzmOWeVZYpHo=; b=XNie4TvmmUwt+KipYRwMFRFgILQ1jwHUOX9R0gwZiMuQod5LUTIzPdE4QMNpaQJtq8 LzUoTud8dsvXgcGckea4/vZk6EY0X+OsYH+dWut+ihWPf3r7qobkH1u3KrStKXm1jHx5 xDdItMIi02rDXQ6yOj0HlV5wc+//9Xs813fFb585nTMbFIJLu4z9B/bOkbbB+X26hiuD rwPUAaU05HRU6/nMttqiX9vqOxbOaP4+EkbBSuYp++EmUSH4P5p0gj6+cvafu9Wm1xA/ McKFU9CQL6pSCGur5Qn5tY7PZMHsvy7b3rMp3CSSI1XwuV8sE3MJQRTPyyJT/HnRKsUf xmBw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=wIf5HJMGnBBFp/6vv4Yo7cE7SjGz9jbwzmOWeVZYpHo=; b=b6NyYqkqaoa71vqeBS0bmO+v/mY5kkQekUJhMEjRshJiGymAhamJ22F05jJtpkWiyk G9pywxVDFxbORvHbCgmDfKS1OUYhsmuNZmgyDwvrQ9W/r+ZPTWHUnLzJSmcK0RLsGIAt NAqoBPwY8ud1JVt0l2RnswHv4Sfwt/wuYibIJQ+zFt0jTBwYAFL6qzQ+XfkCcbIQ08Hz GwN25+D5cQ+pSHqtWNBniImHzDjO9Z2FZ+AB8Jle943QsHpCRYFMEDHv/jcjkzD1H8o/ XyYAk/AHaMQD2drTHZ9tWqAQZXrrRD7mwru1W0yzZxPmkNmGAOk41VWbhchGWGBcDngL K3mg== X-Gm-Message-State: ABuFfogLT4iO+s8pBxBevNxmK9wmkLvkFStLAeOWv7udTHFcG+xamlHA Z+Cz8SFLkkBAyMbRS1SA1v7fgMD9lpO9sjtimCel9tTg X-Google-Smtp-Source: ACcGV6276zOPBxDwFQ1WZDOFIidJWzadUzkpcvigaH7ctO4AvLphnBsKE5gjxjSkBtdguHLc9CkpR3bACUpFLPT2yRY= X-Received: by 2002:a1c:96c7:: with SMTP id y190-v6mr933336wmd.36.1538302624210; Sun, 30 Sep 2018 03:17:04 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Pavel Timofeev Date: Sun, 30 Sep 2018 13:16:52 +0300 Message-ID: Subject: Re: Syslogd less verbose logging with rfc5424 To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Sep 2018 10:17:06 -0000 > Hello, dear community! > > There was a great work to bring rfc5424 date format to syslogd(8). See > https://svnweb.freebsd.org/base?view=revision&revision=332510 > > I've been using it on CURRENT since it was imported. > I'm happy I can finally get syslog messages with high time precision > w/o installing rsyslog or another syslog implementation. > The thing I really don't like is that syslogd puts severity and > priority to log files next to timestamp. > In my opinion severity and priority is not needed in 99% of cases, > only in debugging corner cases. While high precision timestamp is the > main thing what people like rfc 5424 for. This is just my opinion. > So for "-O rfc5424" I'd like to have the same behavior as for rfc > 3164, i. e. do not log severity and priority by default and if needed > use '-v' option to enable those. But it was decided and documented > that '-v' won't have any effect for rfc 5425 > https://svnweb.freebsd.org/base?view=revision&revision=335862 > > The first thing I'd like to suggest is to make rfc 5424 logging the > same way as for rfc 3164, i. e. make '-v' option work the same. > If community is not agree with me, I'd like to suggest another thing: > have another option/flag for syslogd(8) to disable severity and > priority logging if one use rfc 5424. Just for visibility this is how /var/log/message log looks like now if I enable rfc 5424 logging: <2>1 2018-09-30T13:13:14.105894+03:00 nostromo kernel - - - #8 0xffffffff8105f82c at amd64_syscall+0x28c <2>1 2018-09-30T13:13:14.105901+03:00 nostromo kernel - - - #9 0xffffffff8103c14d at fast_syscall_common+0x101 <2>1 2018-09-30T13:13:14.105912+03:00 nostromo kernel - - - Security policy loaded: MAC/ntpd (mac_ntpd) <101>1 2018-09-30T13:13:14.124700+03:00 nostromo ntpd 937 - - ntpd 4.2.8p12-a (1): Starting <101>1 2018-09-30T13:13:14.224314+03:00 nostromo ntpd 938 - - leapsecond file ('/var/db/ntpd.leap-seconds.list'): good hash signature <101>1 2018-09-30T13:13:14.224570+03:00 nostromo ntpd 938 - - leapsecond file ('/var/db/ntpd.leap-seconds.list'): loaded, expire=2018-12-28T00:00:00Z last=2017-01-01T00:00:00Z ofs=37 <13>1 2018-09-30T13:13:14.391787+03:00 nostromo root 990 - - /etc/rc: WARNING: $dbus_enable is not set properly - see rc.conf(5). <28>1 2018-09-30T13:13:14.640885+03:00 nostromo avahi-daemon 1038 - - WARNING: No NSS support for mDNS detected, consider installing nss-mdns!