Re: how to increase space for tmpfs /tmp
- To: firstname.lastname@example.org
- Subject: Re: how to increase space for tmpfs /tmp
- From: Vincent Lefevre <email@example.com>
- Date: Tue, 3 Apr 2012 13:31:21 +0200
- Message-id: <[🔎] 20120403113121.GD8911@xvii.vinc17.org>
- Mail-followup-to: firstname.lastname@example.org
- In-reply-to: <20120328173225.GF30121@codelibre.net>
- References: <CADdDZR=eg_zKg7vy5XJxy3TVwF8N5kYeZJEM4=nyRO7P1VTooA@mail.gmail.com> <20120324152336.GA18436@gnu.kitenet.net> <CALUrRGfNyLUZNqLjbnb8v8K2LD_k7LUgmuSoH2fBQ+wV_G=6nA@mail.gmail.com> <email@example.com> <CALUrRGdKaMg=bYhq4CyQ5mrJJwQWCG6zq2KJkTrXeUYVxO3KeQ@mail.gmail.com> <firstname.lastname@example.org> <20120327131323.GC30121@codelibre.net> <email@example.com> <20120328173225.GF30121@codelibre.net>
On 2012-03-28 18:32:25 +0100, Roger Leigh wrote:
> Applications should not be selfish, and should not blindly fill it.
> Take the streaming media example from earlier today. Is it
> appropriate to dump potentially limitless streams of data to /tmp?
> /Obviously/, it's going to be filled to capacity at some point; any
> application not coping with this /inevitability/ is broken.
> If it's being streamed, isn't buffering sufficient? Otherwise, it
> might as well be termed "downloading". And in the example of /tmp
> being filled by big downloads, is /tmp the appropriate place for
> that, either? I would personally say no. That's not its purpose.
FYI, Firefox/Iceweasel uses /tmp for that. For instance, click on
a link to a PDF file to view it with a PDF viewer; the file is
stored in /tmp. It isn't even removed after the application is
closed (quitting Iceweasel has the effect to remove it, but the
browser can run for several days/weeks).
Vincent Lefèvre <firstname.lastname@example.org> - Web: <http://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)