Neil Bothwick wrote:
> On Sun, 19 Apr 2009 16:47:22 -0500, Dale wrote:
>
>
>> 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:
>>
> [snip]
>
>
>> Why does it not calculate the current compile time correctly? Is this a
>> genlop bug or am I doing something wrong?
>>
>
> The latter, I'm afraid. You've told genlop to look at the old log file,
> but the start time of the current emerge is written to the new log file.
> I use genlop -f when the current log file is in a different location
> (when I'm emerging in a chroot and want to check progress from the
> "parent" OS) and it works fine.
>
> What you are looking for is for genlop to consider multiple log files,
> something it does not currently do. You could file a feature request bug
> report.
>
>
>
I tried this and it works:
r...@smoker / # genlop -f /var/log/emerge.log -f /var/log/emerge.log.old1 -c
using logfile /var/log/emerge.log
using logfile /var/log/emerge.log.old1
Currently merging 1 out of 1
* kde-base/kpat-3.5.10
current merge time: 18 seconds.
ETA: 1 minute and 42 seconds.
r...@smoker / #
So, if I point it to both log files, it sorts out the info rather
nicely. Neat huh? I wouldn't have thought of that without you
explaining how it works tho.
Thanks much ! !
Dale
:-) :-)
