| 1 |
Hi, |
| 2 |
|
| 3 |
I renamed my old emerge log file to .old1 to get off to a fresh start |
| 4 |
with the log file. It was getting pretty large. Anyway, to figure out |
| 5 |
how long something takes to emerge, I use this command and get this |
| 6 |
response: |
| 7 |
|
| 8 |
root@smoker / # genlop -f /var/log/emerge.log.old1 -c |
| 9 |
using logfile /var/log/emerge.log.old1 |
| 10 |
|
| 11 |
Currently merging 1 out of 4 |
| 12 |
|
| 13 |
* sys-libs/glibc-2.8_p20080602-r1 |
| 14 |
|
| 15 |
current merge time: 3 hours, 18 minutes and 43 seconds. |
| 16 |
ETA: any time now. |
| 17 |
root@smoker / # |
| 18 |
|
| 19 |
One, that emerge started about 15 or 20 minutes ago. If I use this |
| 20 |
command, it works pretty well. |
| 21 |
|
| 22 |
root@smoker / # genlop -f /var/log/emerge.log.old1 -t glibc |
| 23 |
using logfile /var/log/emerge.log.old1 |
| 24 |
* sys-libs/glibc |
| 25 |
|
| 26 |
Mon Apr 6 17:06:47 2009 >>> sys-libs/glibc-2.8_p20080602-r1 |
| 27 |
merge time: 43 minutes and 32 seconds. |
| 28 |
|
| 29 |
Wed Apr 15 23:45:07 2009 >>> sys-libs/glibc-2.8_p20080602-r1 |
| 30 |
merge time: 1 hour, 3 minutes and 58 seconds. |
| 31 |
|
| 32 |
Thu Apr 16 14:20:03 2009 >>> sys-libs/glibc-2.8_p20080602-r1 |
| 33 |
merge time: 52 minutes and 17 seconds. |
| 34 |
|
| 35 |
Fri Apr 17 07:40:28 2009 >>> sys-libs/glibc-2.8_p20080602-r1 |
| 36 |
merge time: 44 minutes and 46 seconds. |
| 37 |
|
| 38 |
Sun Apr 19 14:59:35 2009 >>> sys-libs/glibc-2.8_p20080602-r1 |
| 39 |
merge time: 1 hour, 38 minutes and 22 seconds. |
| 40 |
|
| 41 |
root@smoker / # |
| 42 |
|
| 43 |
Why does it not calculate the current compile time correctly? Is this a |
| 44 |
genlop bug or am I doing something wrong? Has anyone else ran into this |
| 45 |
before? It has been this way for quite a while now. I recall a year or |
| 46 |
so ago it doing this but just ignored it. |
| 47 |
|
| 48 |
Thanks. |
| 49 |
|
| 50 |
Dale |
| 51 |
|
| 52 |
:-) :-) |
Archives