Mailinglist Archive: opensuse-factory (715 mails)

[Frederic Crozat <fcrozat@xxxxxxxx>]

Le mercredi 28 mars 2012 à 13:15 +0200, Andreas Jaeger a écrit :
> On 03/28/2012 01:04 PM, Frederic Crozat wrote:
> > Le mercredi 28 mars 2012 à 12:48 +0200, Takashi Iwai a écrit :
> > > At Wed, 28 Mar 2012 11:54:53 +0200,
> > > Frederic Crozat wrote:
> > > > Le mardi 27 mars 2012 à 20:27 -0300, Claudio Freire a écrit :
> > > >
> > > > > In low memory devices, with /tmp as tmpfs, think 1G, brasero, k3b and
> > > > > a few other programs, in their default configuration, would thrash.
> > > > > Those are blatantly wrong cases. But there are numerous gray cases.
> > > > > Python's tempfile module creates, by default, files in /tmp. I would
> > > > > bet tons of python apps, thus, misuse /tmp.
> > > >
> > > > We should fix those "known" programs to use /var/tmp instead of /tmp
> > > > anyway.
> > >
> > > Notorious acroread and flashplayer are such "known" programs, too.
> > > IIRC, flashplayer may store a temporary FLV file in /tmp, which can be
> > > unlimitedly big.
> >
> > Do they hardcode /tmp or use TMPDIR ? That would be interesting to know.
>
> Running strings on /usr/lib64/browser-plugins/libflashplayer.so I found 
> no match for TMPDIR but these:
> /tmp/putH
> /tmp/FlaH
> /tmp/FlaH
> /tmp/crl
>
> A readelf -s shows that the library uses mkstemp - where the developers 
> needs to supply a path.
>
>
> > > Honestly, someone needs to test carefully (e.g. on a machine with
> > > small RAM) before moving toward this direction as default.
> > > Only facts and proofs can shut up bike-shed talks.
> >
> > Agreed.
>
> I propose to collect the options and questions we have at one place in 
> the wiki,

I've created a blank page for now on http://en.opensuse.org/Tmp-on-tmpfs

I'll try to fill it with the various informations I got here and from
Debian and Gentoo folks.

-- 
Frederic Crozat <fcrozat@xxxxxxxx>
SUSE

-- 
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-factory+owner@xxxxxxxxxxxx