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

List:       kde-core-devel
Subject:    Re: konsole disk usage
From:       Hans Meine <hans_meine () gmx ! net>
Date:       2000-05-26 13:01:56
[Download RAW message or body]

Richard Moore <rich@ipso-facto.freeserve.co.uk> writes:

> 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
> 
> They are usually the result of a memory dump that includes pages the user who created the dump
> did not have permission to view. For example if the user only had execute permissions.

AFAIK at this moment, you can _only_ create them by seek()ing beyond 
filesize. In no other way. :-( It even is filled with "0"s by standard
cp, since holes deliver zeros when read. :-(

In konsole case, there must be another way round.

-- 

   /  /
  /--/
 /  / ANS
___________________________________________________________________________
 Hans Meine   Wördemannsweg 93, D-22527 Hamburg  mailto:hans_meine@gmx.net

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