/tmp on tmpfs

[Reindl Harald]

Am 06.04.2012 20:50, schrieb Chris Murphy:
> 
> On Apr 6, 2012, at 8:03 AM, Vratislav Podzimek wrote:
>>>> That a lost fight, because one of /tmp's primary purposes is to 
>>> temporarily store almost arbitrarily huge amounts of data, instead of 
>>> storing them in memory.
>> This is the key overlooked fact.
> 
> What happens to /tmp on tmpfs when real memory and swap are completely consumed? I think the key overlooked fact is the possibility some application asks for a lot more /tmp space than is ever reserved for swap. Example:
> 
> I'd expect Brisera to produce an ~9GB temp file when burning a fully consumed dual-layer DVD. Incorrect assumption? Minimum requirements for Fedora 16, 1152MB RAM. That translates into what default for swap space? Is this at least 4GB, or whatever the minimum amount of swap needed for tmpfs when full to overflow to?
> 
> Does anyone know what the behavior of Scribus, GIMP, Cinelerra, etc. are when it comes to temp space requirements? I could see GIMP arbitrarily want multiple gigabytes of space, well beyond physical RAM plus that reserved for swap space.

the developers of this "feature" try to explain us that applications
should stop using /tmp and put their stuff in /var/tmp to make the
"feature" possible

as longer i think about the idea having /tmp in memory as default
as lesser sense this idea is making for me

however, as long my enry in /etc/fstab is honored all the users
with default setups does not bother me, but that does not
make things better for the overall quality of the distribution

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
URL: <http://lists.fedoraproject.org/pipermail/devel/attachments/20120406/b426ea29/attachment.sig>