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