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

List:       kde-core-devel
Subject:    Re: [PATCH] Konsole, changing history size.
From:       Scott Manson <Maniac () Alltel ! net>
Date:       2001-07-25 5:09:53
[Download RAW message or body]

On Monday 23 July 2001 05:54 pm, Guillaume Laurent wrote:
> On Tuesday 24 July 2001 00:38, Waldo Bastian wrote:
> > On Monday 23 July 2001 03:00 pm, Guillaume Laurent wrote:
> > > I suggest we re-enable infinite, file-based history as an option along
> > > with the memory-based one we have right now,
> >
> > Yes, we can let size=0 show "Unlimited" or something. Does that introduce
> > a new string?
>
> On one hand I like the idea of hiding the two implementations behind an
> identical configuration, but on the other since both have different
> implications (one will fill your hd), I'd rather make things really clear.
>
> > Whether the file is pre-deleted or not doesn't make much difference.
>
> It does, because then you have users which wonder why their df says their
> /tmp is full while neither ls or du report any file large enough to account
> for the lost space.
>
> > When
> > the user deletes the file nothing will happen as long as the file is
> > still open. It only increases the chance that the file will not be
> > deleted at all.
>
> Yes, that is a problem. If konsole crashes or is killed, the history file
> will stay. So may be still pre-deleting the file but issuing a warning
> about this is the best solution ("if your /tmp is full, exit konsole or
> clear history").
This is the wrong way about it. I know that the "newbies" shouldn't/wouldn't
worry about a directory being full but can we find another solution that 
avoids this fsck-up? Most newbies don't realize that when you decide to 
partition space that the /tmp dir is part of "/" so a lot of mistakes are not 
making the / partition large enough they look and say hey / only *needs* 500 
Mb so that's all I'll make it after install they see that they have say 100Mb 
free and say that should be enough but then the try an run some programs that 
steal some space from / which they really have less than they think then they 
are going to be either confused or *pissed* as they keep getting messages 
that their /tmp directory if full please delete some files and .... 

IMHO KDE should not make any assumptions about the filesystem (about whether 
to store some files here or there) I can also think about the /var problem 
where cache files are taking up space.
I know that we can't read the minds of every user and such but if we decided 
to start to store everything under the "/home/$USER directory we could have a 
better system as it doesn't care how many other user(s) have used up the /tmp 
space w/o then bothering the sysadmin to IMHO "clean up" the system.

As much as we want to think that we are only serving *1* user at a time we 
have to remember that we are running on a multiuser system and minimize our 
usage of "global" resources so we can "serve" more with less and without 
bothering the "whole" box/system.

-- 
Maniac@alltel.net 40° 37' 9" N, 96° 57' 24" W  
A single tasking guy in multi tasking world.

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