From owner-freebsd-questions@freebsd.org Sat Mar 12 08:18:37 2016 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EBE34ACDF6E for ; Sat, 12 Mar 2016 08:18:37 +0000 (UTC) (envelope-from trashcan@ellael.org) Received: from mx2.enfer-du-nord.net (mx2.enfer-du-nord.net [IPv6:2001:41d0:d:3049:1:1:0:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BB1F57C7 for ; Sat, 12 Mar 2016 08:18:37 +0000 (UTC) (envelope-from trashcan@ellael.org) Received: from [IPv6:2003:8c:2e3b:5c01:f4d0:b54:948b:d34e] (p2003008C2E3B5C01F4D00B54948BD34E.dip0.t-ipconnect.de [IPv6:2003:8c:2e3b:5c01:f4d0:b54:948b:d34e]) by mx2.enfer-du-nord.net (Postfix) with ESMTPSA id 3qMcNC5JYFz9YT for ; Sat, 12 Mar 2016 09:18:35 +0100 (CET) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\)) Subject: Re: reported timestamps during boot process? From: Michael Grimm In-Reply-To: <20160312074705.568f20a8@X220.alogt.com> Date: Sat, 12 Mar 2016 09:18:35 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <25D3B6C6-6640-4F17-9204-3AF2F4799CE9@ellael.org> References: <20160312074705.568f20a8@X220.alogt.com> To: FreeBSD Questions X-Virus-Scanned: clamav-milter 0.99 at mail X-Virus-Status: Clean X-Mailer: Apple Mail (2.3112) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Mar 2016 08:18:38 -0000 Erich Dollansky wrote: > Michael Grimm wrote: >> Is there a way to investigate the boot process by means of reported >> timestamps in some logfile? dmesg doesn't seem to be the tool of >> choice. > you might find some hints in /var/log/messages. Nope. It looks to me [1] that, whilst booting, kernel messages are = written to that file in one batch after syslogd has been fired up. = Timestamps of those messages are all showing the very same second. Linux' dmesg has such a feature [2] I am looking for: | -d, --show-delta | | Display the timestamp and the time delta spent between | messages. If used together with =E2=80=94notimee then = only the time | delta without the timestamp is printed. Regards, Michael [1] is that correct? [2] http://man7.org/linux/man-pages/man1/dmesg.1.html=