> gnome-terminal stores the scrollback content in a temporary file, opened
> at the standard location which is /tmp by default, overridable with the
> standard TMPDIR environment variable

this default/standard location /tmp is certainly inadmissible, since it's
an obvious welcome hackers breach. Users should be restricted to use their
own quotas, even for the g-t. If there are thousands applications being
regularly used on a system which behave similarly, should all of them be
audited and reconfigured against such gotchas?



On Mon, May 19, 2014 at 10:39 PM, Egmont Koblinger <email address hidden> wrote:

> > The question is this: why does it overflow the / rather than the /home
> partition?
>
> gnome-terminal stores the scrollback content in a temporary file, opened
> at the standard location which is /tmp by default, overridable with the
> standard TMPDIR environment variable.
>
> > May be "unlimited" should be understood as "unlimited within
> reasonable limits"?
>
> g-t tries to do what you ask from this. If you ask this to remember
> everything, it tries to store everything. What do you mean by
> "reasonable limits"? E.g. 1 million lines? Feel free to set this in
> gnome-terminal's preferences :)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1320157
>
> Title:
>   user space gnome-terminal overflows / file system
>
> Status in “gnome-terminal” package in Ubuntu:
>   New
>
> Bug description:
>   I have two partitions on my system:
>
>   $ df -h
>   Filesystem Size Used Avail Use% Mounted on
>   /dev/sda3 23G 12G 11G 52% /
>   /dev/sda6 98G 67G 27G 72% /home
>
>   When I run a user application (on /home) which produces lots of
>   debugging output to the terminal, it quickly (less than a day)
>   overflows the root file system /. I think I figured the reason for
>   that:
>
>   I selected the "unlimited" option for scrolling back in the gnome
>   terminal.
>
>   The question is this: why does it overflow the / rather than the /home
>   partition? May be "unlimited" should be understood as "unlimited
>   within reasonable limits"?
>
>   I earlier reported it as
>
>   https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1319667
>
>   (Of course I am not going to use this in a production application. It
>   popped up in a stress testing, where I modeled events which happen
>   usually once or twice a minute at accelerated speed, of thousands of
>   times per second)
>
>   1)
>   $ lsb_release -rd
>   Description:  Ubuntu 14.04 LTS
>   Release:      14.04
>
>   2)
>   # apt-cache policy gnome-terminal
>   gnome-terminal:
>     Installed: 3.6.2-0ubuntu1
>     Candidate: 3.6.2-0ubuntu1
>     Version table:
>    *** 3.6.2-0ubuntu1 0
>           500 http://se.archive.ubuntu.com/ubuntu/ trusty/main amd64
> Packages
>           100 /var/lib/dpkg/status
>
>   3) I expected it to chop off the terminal output when it grew
>   unreasonably big, or at least not to overflow the / partition, staying
>   in /home instead.
>
>
>   4) it overflew the / partition instead
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 14.04
>   Package: gnome-terminal 3.6.2-0ubuntu1
>   ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
>   Uname: Linux 3.13.0-24-generic x86_64
>   ApportVersion: 2.14.1-0ubuntu3
>   Architecture: amd64
>   Date: Fri May 16 11:18:01 2014
>   InstallationDate: Installed on 2014-02-10 (94 days ago)
>   InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64
> (20131016.1)
>   SourcePackage: gnome-terminal
>   UpgradeStatus: Upgraded to trusty on 2014-04-22 (24 days ago)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1320157/+subscriptions
>