[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: konsole disk usage
From:       Mario Weilguni <mweilguni () sime ! com>
Date:       2000-05-26 19:53:29
[Download RAW message or body]

What's the point of discussing this here? It can't be solved by working on 
spare files, so why bother?

I looked into TEKonsole.C which is responsible for this, but's it's not easy 
to solve. Maybe tomorrow I'll have more time to check it.

Ciao,
	Mario


Am Fre, 26 Mai 2000 schrieb Uwe Thiem:
> On Thu, 25 May 2000, Waldo Bastian wrote:
> > On Thu, 25 May 2000, Preston Brown wrote:
> > > konsole still has the annoying tendency to use up TONS of disk on the
> > > /tmp filesystem when it has been running for awhile.  I believe this is
> > > related to the history mechanism.
> > >
> > > If you have a 100meg root filesystem, this is CRIPPLING.  Can someone
> > > who actually understands the problem fix it, or at least introduce an
> > > optional limit?
> >
> > Hm.. I can imagine how it works.. (just append to a file) and it's not
> > straightfoward to discard stuff from the start of the file then.
> >
> > Weird idea: Although /ext2 allows you to have empty blocks in a file, I
> > have no idea how to create them afterwards
>
> No straight forward way. You can copy the file to a new one 'till the
> position where you want the "hole". Then re-position the the write index
> for the new file and copy the rest. Them mv the new file to the old
> one. Only way I know of.
>
> Uwe
>
> -------------------------------------------------------------------------
> Uwe Thiem                                        Tel:  +264 - 61 - 249249
> P.O.Box 30955                                    Email:   uwe@uwix.alt.na
> Windhoek                                                      uwe@kde.org
> Republic of Namibia                                    http://www.kde.org
>                   **********************************
>          You can still escape from the GATES of hell: Use KDE!
> -------------------------------------------------------------------------

[prev in list] [next in list] [prev in thread] [next in thread]