From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id AEF29138CA3 for ; Thu, 5 Mar 2015 12:01:29 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 0AB6DE08BD; Thu, 5 Mar 2015 12:01:17 +0000 (UTC) Received: from mail0200.smtp25.com (mail0200.smtp25.com [174.37.170.200]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id EFAF3E07FD for ; Thu, 5 Mar 2015 12:01:15 +0000 (UTC) Received: from ccs.covici.com (localhost [127.0.0.1]) by ccs.covici.com (8.14.9/8.14.8) with ESMTP id t25C1Cbi018826 for ; Thu, 5 Mar 2015 07:01:12 -0500 From: covici@ccs.covici.com To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] See bootup/poweroff screen? In-reply-to: <54F81F07.1030704@gmail.com> References: <20150304215839.f23ab34e4ac7c30e4685c392@gmail.com> <54F7F4FE.5050902@gmail.com> <20150305030846.24cb9b0c54af337c17e3c863@gmail.com> <20150305082556.4aca38c9@digimed.co.uk> <54F81F07.1030704@gmail.com> Comments: In-reply-to Dale message dated "Thu, 05 Mar 2015 03:16:55 -0600." X-Mailer: MH-E 8.5; nmh 1.6; GNU Emacs 23.4.1 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <18822.1425556872.1@ccs.covici.com> Date: Thu, 05 Mar 2015 07:01:12 -0500 Message-ID: <18823.1425556872@ccs.covici.com> X-SpamH-OriginatingIP: 70.109.53.110 X-SpamH-Filter: s-out-001.smtp25.com-t25C1DFF020959 X-Archives-Salt: 7f002bd2-2fe7-4150-b370-8242a22d9cdb X-Archives-Hash: 9929a12f7e9a0879dafa51e25f125bb3 Dale wrote: > Neil Bothwick wrote: > > On Thu, 5 Mar 2015 03:08:46 -0500, German wrote: > > > >> Thanks Dale, done it. Unfortunately it doesn't log everything. For > >> instance "Warning: /lib64/rc/cache is not writable" wasn't written > >> to /var/log/rc.log > > > > Of course it wasn't. Warnings about /var not being writeable are not going > > to be written to /var. > > > > > > Yea, it won't catch everything. This is sort of designed for that point > where one log stops and the other hasn't started yet. This is usually > where dmesg stops and syslog and friends hasn't yet started. Of course, > if /var isn't mounted, well, it has no where to go. > > Isn't those init thingys supposed to fix this sort of thing tho? Isn't > it supposed to store it in memory until /var is mounted and then dump it? Make sure your kernel log buffer is as high as it will go, I use 21 if memory serves which is about a meg or so. Also, I find with an init thingy and using systemd (Yes I know, don't start a flame war), then I see everything in its system journal -- much more even than rc.log used to give me. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici covici@ccs.covici.com