| 1 |
Neil Bothwick wrote: |
| 2 |
> On Sun, 19 Apr 2009 16:47:22 -0500, Dale wrote: |
| 3 |
> |
| 4 |
> |
| 5 |
>> I renamed my old emerge log file to .old1 to get off to a fresh start |
| 6 |
>> with the log file. It was getting pretty large. Anyway, to figure out |
| 7 |
>> how long something takes to emerge, I use this command and get this |
| 8 |
>> response: |
| 9 |
>> |
| 10 |
> [snip] |
| 11 |
> |
| 12 |
> |
| 13 |
>> Why does it not calculate the current compile time correctly? Is this a |
| 14 |
>> genlop bug or am I doing something wrong? |
| 15 |
>> |
| 16 |
> |
| 17 |
> The latter, I'm afraid. You've told genlop to look at the old log file, |
| 18 |
> but the start time of the current emerge is written to the new log file. |
| 19 |
> I use genlop -f when the current log file is in a different location |
| 20 |
> (when I'm emerging in a chroot and want to check progress from the |
| 21 |
> "parent" OS) and it works fine. |
| 22 |
> |
| 23 |
> What you are looking for is for genlop to consider multiple log files, |
| 24 |
> something it does not currently do. You could file a feature request bug |
| 25 |
> report. |
| 26 |
> |
| 27 |
> |
| 28 |
> |
| 29 |
|
| 30 |
I tried this and it works: |
| 31 |
|
| 32 |
root@smoker / # genlop -f /var/log/emerge.log -f /var/log/emerge.log.old1 -c |
| 33 |
using logfile /var/log/emerge.log |
| 34 |
using logfile /var/log/emerge.log.old1 |
| 35 |
|
| 36 |
Currently merging 1 out of 1 |
| 37 |
|
| 38 |
* kde-base/kpat-3.5.10 |
| 39 |
|
| 40 |
current merge time: 18 seconds. |
| 41 |
ETA: 1 minute and 42 seconds. |
| 42 |
root@smoker / # |
| 43 |
|
| 44 |
So, if I point it to both log files, it sorts out the info rather |
| 45 |
nicely. Neat huh? I wouldn't have thought of that without you |
| 46 |
explaining how it works tho. |
| 47 |
|
| 48 |
Thanks much ! ! |
| 49 |
|
| 50 |
Dale |
| 51 |
|
| 52 |
:-) :-) |
Archives