From mboxrd@z Thu Jan 1 00:00:00 1970
Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org)
by finch.gentoo.org with esmtp (Exim 4.60)
(envelope-from <gentoo-user+bounces-132787-garchives=archives.gentoo.org@lists.gentoo.org>)
id 1Re8Hl-0003R1-Rd
for garchives@archives.gentoo.org; Fri, 23 Dec 2011 16:47:58 +0000
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id 7D5C921C0A4;
Fri, 23 Dec 2011 16:47:44 +0000 (UTC)
Received: from svr-us4.tirtonadi.com (svr-us4.tirtonadi.com [69.65.43.212])
by pigeon.gentoo.org (Postfix) with ESMTP id BD21E21C163
for <gentoo-user@lists.gentoo.org>; Fri, 23 Dec 2011 16:46:32 +0000 (UTC)
Received: from mail-wi0-f181.google.com ([209.85.212.181])
by svr-us4.tirtonadi.com with esmtpsa (TLSv1:RC4-SHA:128)
(Exim 4.69)
(envelope-from <pandu@poluan.info>)
id 1Re8GR-000fh0-2x
for gentoo-user@lists.gentoo.org; Fri, 23 Dec 2011 23:46:35 +0700
Received: by wibhq2 with SMTP id hq2so3798583wib.40
for <gentoo-user@lists.gentoo.org>; Fri, 23 Dec 2011 08:46:28 -0800 (PST)
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@lists.gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
MIME-Version: 1.0
Received: by 10.180.19.138 with SMTP id f10mr42885639wie.3.1324658788900; Fri,
23 Dec 2011 08:46:28 -0800 (PST)
Received: by 10.223.103.70 with HTTP; Fri, 23 Dec 2011 08:46:28 -0800 (PST)
Received: by 10.223.103.70 with HTTP; Fri, 23 Dec 2011 08:46:28 -0800 (PST)
In-Reply-To: <loom.20111223T173338-198@post.gmane.org>
References: <20111221174800.GA2778@acm.acm>
<2433401.6esHuO028t@powerslave>
<20111222140626.GC3361@acm.acm>
<loom.20111223T173338-198@post.gmane.org>
Date: Fri, 23 Dec 2011 23:46:28 +0700
Message-ID: <CAA2qdGWjnbLcL6YyHC0x-Uy0NvZAfD+hHKP0HqYuoRdAEkgq+A@mail.gmail.com>
Subject: Re: [gentoo-user] Re: Which log file do all the emerge messages get
saved in?
From: Pandu Poluan <pandu@poluan.info>
To: gentoo-user@lists.gentoo.org
Content-Type: multipart/alternative; boundary=bcaec53d550d8fa02e04b4c52857
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - svr-us4.tirtonadi.com
X-AntiAbuse: Original Domain - lists.gentoo.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - poluan.info
X-Archives-Salt: 519abc6c-7258-447f-b68d-accba150f8bd
X-Archives-Hash: a7330393b6b836e25c5a638c7cffc57b
--bcaec53d550d8fa02e04b4c52857
Content-Type: text/plain; charset=UTF-8
On Dec 23, 2011 11:41 PM, "James" <wireless@tampabay.rr.com> wrote:
>
> Alan Mackenzie <acm <at> muc.de> writes:
>
> > > > The messages which stream by during an emerge, in particular the
> > > > warnings etc. which are repeated at the end of a single emerge
> > > > operation. They're accumulated in a log file somewhere, aren't
they?
>
> > > /var/log/portage/elog/summary.log
>
> If you want a finer granularity of control, just set it up
> in /etc/make.conf
>
> Here's an example I use on one system:
>
> ## LOGGING Control of Ebuilds
> PORT_LOGDIR="/var/log/elog/"
> PORTAGE_ELOG_CLASSES="info log error"
> PORTAGE_ELOG_SYSTEM="save"
>
> Lots of ways to customize the logging of what you emerge.
> hth,
> James
>
>
... and emerge elogv. Makes reading portage info/warns/errors easier thanks
to its colorful ncurses interface :-)
Rgds,
--bcaec53d550d8fa02e04b4c52857
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<p><br>
On Dec 23, 2011 11:41 PM, "James" <<a href=3D"mailto:wireless@=
tampabay.rr.com">wireless@tampabay.rr.com</a>> wrote:<br>
><br>
> Alan Mackenzie <acm <at> <a href=3D"http://muc.de">muc.de</a>=
> writes:<br>
><br>
> > > > The messages which stream by during an emerge, in parti=
cular the<br>
> > > > warnings etc. which are repeated at the end of a single=
emerge<br>
> > > > operation. =C2=A0They're accumulated in a log file =
somewhere, aren't they?<br>
><br>
> > > /var/log/portage/elog/summary.log<br>
><br>
> If you want a finer granularity of control, just set it up<br>
> in /etc/make.conf<br>
><br>
> Here's an example I use on one system:<br>
><br>
> ## LOGGING Control of Ebuilds<br>
> PORT_LOGDIR=3D"/var/log/elog/"<br>
> PORTAGE_ELOG_CLASSES=3D"info log error"<br>
> PORTAGE_ELOG_SYSTEM=3D"save"<br>
><br>
> Lots of ways to customize the logging of what you emerge.<br>
> hth,<br>
> James<br>
><br>
></p>
<p>... and emerge elogv. Makes reading portage info/warns/errors easier tha=
nks to its colorful ncurses interface :-) </p>
<p>Rgds,<br>
</p>
--bcaec53d550d8fa02e04b4c52857--