Mailinglist Archive: opensuse-factory (715 mails)
| < Previous | Next > |
Re: [opensuse-factory] Warning / ANNOUNCE : upcoming changes in upstream systemd regarding /media, /tmp and /var/run | /var/lock
- From: Ludwig Nussel <ludwig.nussel@xxxxxxx>
- Date: Wed, 28 Mar 2012 18:05:05 +0200
- Message-id: <4F7336B1.1030206@suse.de>
Frederic Crozat wrote:
And the third possibility would be to have the pam module create $TMPDIR
on persistent storage somewhere below /var. That would avoid the trouble
with NFS and not put anything into RAM.
I wonder what kind of data actually ends up in TMPDIR if we separate
it from /tmp and applications start honoring $XDG_DOWNLOAD_DIR and
$XDG_CACHE_HOME though.
cu
Ludwig
--
(o_ Ludwig Nussel
//\
V_/_ http://www.suse.de/
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB
16746 (AG Nürnberg)
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-factory+owner@xxxxxxxxxxxx
Le mercredi 28 mars 2012 à 14:05 +0200, Ludwig Nussel a écrit :
Richard Guenther wrote:
On Tue, 27 Mar 2012, Frederic Crozat wrote:
[...]
Btw, I see that TMPDIR is /tmp by default on 12.1. GCC uses this
for all temporary files, for link-time optimizing firefox for
example you need about 4GB of storage in TMPDIR.
Thus, consider that (apart from my own personal opinion that a
stateless /tmp is utterly stupid, a tmpfs /tmp is even more so).
So, change TMPDIR to point to /var/tmp? Which would of course
make /tmp quite useless.
Independent of whether or not to use tmpfs for /tmp from security PoV it
would be desirable to set TMPDIR to a per user directory rather than one
global 1777 dir to avoid tmp races in sloppy programmed applications.
This is something we are doing at Mandrake / Mandriva for years (using
TMPDIR=$HOME/tmp), but it has also its set of issues :
- it didn't play nice at all with network mounted home
- we had to patch some software (I remember gconf or ORBit) to make sure
they were still using a "always local" TMPDIR and not one which could be
shared across system.
One possibility could be to use /run/<user>/ hierarchy which is now
created by pam_systemd at login and erased at logout.
And the third possibility would be to have the pam module create $TMPDIR
on persistent storage somewhere below /var. That would avoid the trouble
with NFS and not put anything into RAM.
I wonder what kind of data actually ends up in TMPDIR if we separate
it from /tmp and applications start honoring $XDG_DOWNLOAD_DIR and
$XDG_CACHE_HOME though.
cu
Ludwig
--
(o_ Ludwig Nussel
//\
V_/_ http://www.suse.de/
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB
16746 (AG Nürnberg)
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-factory+owner@xxxxxxxxxxxx
| < Previous | Next > |