| 1 |
On 10/05/06, Neil Bothwick <neil@××××××××××.uk> wrote: |
| 2 |
> On Tue, 9 May 2006 18:22:24 -0700, Daevid Vincent wrote: |
| 3 |
> |
| 4 |
> > In /etc/make.conf I have PORT_LOGDIR="/var/tmp/portage-logs" |
| 5 |
> > |
| 6 |
> > This is great in that I can then read through the billions of .log |
| 7 |
> > files to see if there are any post install manual tasks I have to do. |
| 8 |
> > |
| 9 |
> > However, a good majority of them are just compilation output. I really |
| 10 |
> > don't need or care to see those -- especially if the compilation |
| 11 |
> > concluded sans errors. |
| 12 |
> > |
| 13 |
> > I just want the juicy ones. The ones that tell me to take further |
| 14 |
> > action. |
| 15 |
> |
| 16 |
> There are two log files for each emerge, the smaller one contains the |
| 17 |
> "juicy" bits. |
| 18 |
> |
| 19 |
> The latest portage, still in testing, has an option to save the relevant |
| 20 |
> messages to a log directory or email them to you. You can choose the |
| 21 |
> level of messages you receive; info, warn or error. |
| 22 |
|
| 23 |
There's also enotice - although I think its deprecated? |
| 24 |
|
| 25 |
A crude way of only checking the warning log files is by making a |
| 26 |
judgment call on their size: |
| 27 |
========================= |
| 28 |
-rw-r--r-- 1 root portage 18944 May 6 12:12 3799-rsync-2.6.8.log |
| 29 |
-rw-r--r-- 1 root portage 0 May 6 12:13 3800-rsync-2.6.0-r6.log |
| 30 |
-rw-r--r-- 1 root portage 270 May 6 12:13 3800-rsync-2.6.8.log |
| 31 |
========================= |
| 32 |
|
| 33 |
In the above example the last entry (270 bytes) is what you need to |
| 34 |
read. The first @ 18944 bytes is the compilation and make/install |
| 35 |
output and the middle one would normally contain any error/warning |
| 36 |
messages relevant to uninstalling the previous version. |
| 37 |
-- |
| 38 |
Regards, |
| 39 |
Mick |
| 40 |
|
| 41 |
-- |
| 42 |
gentoo-user@g.o mailing list |
Archives