From owner-freebsd-hackers@freebsd.org Sun Apr 1 03:25:41 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 5A13BF77409 for ; Sun, 1 Apr 2018 03:25:41 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id EE13486300 for ; Sun, 1 Apr 2018 03:25:40 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from Julian-MBP3.local (115-166-20-68.dyn.iinet.net.au [115.166.20.68]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id w313Pa79042014 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Sat, 31 Mar 2018 20:25:39 -0700 (PDT) (envelope-from julian@freebsd.org) Subject: Re: Add option -Z to syslogd(8) to use ISO 8601 timestamps To: Ben Woods , "freebsd-hackers@freebsd.org" References: From: Julian Elischer Message-ID: <4fd424ca-ff93-315c-fa87-fb9c738b9b50@freebsd.org> Date: Sun, 1 Apr 2018 11:25:30 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Apr 2018 03:25:41 -0000 On 1/4/18 8:27 am, Ben Woods wrote: > Hi everyone, > > Please review my patch to add the -Z option to syslogd(8) to use ISO 8601 > timestamps in UTC: YES!  I was just looking into doing this myself.. Just goes to show that if one procrastinates enough, someone else will do the work! is there a matching change for syslog(3) to actually generate new timestamps? The syslog protocol is unique that either end can be responsible for the timestamp. In the case of the new timestamp form you would have to strip off the incoming old form timestamp and replace it.