Neil Bothwick wrote:
> On Tue, 21 Apr 2009 02:41:02 -0500, Dale wrote:
>
>
>> So, if I point it to both log files, it sorts out the info rather
>> nicely. Neat huh?
>>
>
> It gets neater, according to the man page
>
> If you rotate emerge.log you could use:
> genlop -tu -f /var/log/emer
On Tue, 21 Apr 2009 02:41:02 -0500, Dale wrote:
> So, if I point it to both log files, it sorts out the info rather
> nicely. Neat huh?
It gets neater, according to the man page
If you rotate emerge.log you could use:
genlop -tu -f /var/log/emerge.log -f /var/log/emerge.log.0
-f /var/log/em
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
>>
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
>>
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
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/
6 matches
Mail list logo
