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

List:       kde-core-devel
Subject:    Re: [PATCH] Konsole, changing history size.
From:       Guillaume Laurent <glaurent () telegraph-road ! org>
Date:       2001-07-25 6:52:03
[Download RAW message or body]

On Wednesday 25 July 2001 07:09, Scott Manson wrote:
> On Monday 23 July 2001 05:54 pm, Guillaume Laurent wrote:
>
> > 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 "/"

No, /tmp can perfectly be on its own partition, and partitionning a HD is 
hardly newbie-level stuff.

> 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

NFS-mounted home dirs are quite common, which is totally inadequate for 
something like the konsole history file. NFS is too fragile and too slow for 
this.

> 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.

What cleaning ? There's no cleaning involved with the current file-based 
history mechanism. The file will go away as soon as the process dies.

-- 
					Guillaume.
					http://www.telegraph-road.org

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