Evening, all.

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?

I can't find this file anymore. I've looked in /var/log,
/var/lib/portage, but find nothing.

Would some kind soul please identify this log file for me. Thanks!

--
Alan Mackenzie (Nuremberg, Germany).

On Wednesday 21 Dec 2011 17:48:00 Alan Mackenzie wrote:

> Evening, all.

>

> 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?

>

> I can't find this file anymore. I've looked in /var/log,

> /var/lib/portage, but find nothing.

>

> Would some kind soul please identify this log file for me. Thanks!

*

/var/log/portage/elog/summary.log

*



*

--

*

- Yohan Pereira

*

"A man can do as he will, but not will as he will" - Schopenhauer

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,