| 1 |
On Dec 23, 2011 11:41 PM, "James" <wireless@×××××××××××.com> wrote: |
| 2 |
> |
| 3 |
> Alan Mackenzie <acm <at> muc.de> writes: |
| 4 |
> |
| 5 |
> > > > The messages which stream by during an emerge, in particular the |
| 6 |
> > > > warnings etc. which are repeated at the end of a single emerge |
| 7 |
> > > > operation. They're accumulated in a log file somewhere, aren't |
| 8 |
they? |
| 9 |
> |
| 10 |
> > > /var/log/portage/elog/summary.log |
| 11 |
> |
| 12 |
> If you want a finer granularity of control, just set it up |
| 13 |
> in /etc/make.conf |
| 14 |
> |
| 15 |
> Here's an example I use on one system: |
| 16 |
> |
| 17 |
> ## LOGGING Control of Ebuilds |
| 18 |
> PORT_LOGDIR="/var/log/elog/" |
| 19 |
> PORTAGE_ELOG_CLASSES="info log error" |
| 20 |
> PORTAGE_ELOG_SYSTEM="save" |
| 21 |
> |
| 22 |
> Lots of ways to customize the logging of what you emerge. |
| 23 |
> hth, |
| 24 |
> James |
| 25 |
> |
| 26 |
> |
| 27 |
|
| 28 |
... and emerge elogv. Makes reading portage info/warns/errors easier thanks |
| 29 |
to its colorful ncurses interface :-) |
| 30 |
|
| 31 |
Rgds, |
Archives