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: Robert Schweikert <rjschwei@xxxxxxxx>
- Date: Wed, 28 Mar 2012 09:39:59 -0400
- Message-id: <4F7314AF.email@example.com>
On 03/28/2012 07:10 AM, Frederic Crozat wrote:
Le mercredi 28 mars 2012 à 11:10 +0100, Ruediger Meier a écrit :
On Wednesday 28 March 2012, Frederic Crozat wrote:
Le mercredi 28 mars 2012 à 10:30 +0100, Adam Spiers a écrit :
Cristian Rodríguez (crrodriguez@xxxxxxxxxxxx) wrote:
El 27/03/12 20:54, Carlos E. R. escribió:
On 2012-03-28 01:27, Cristian Rodríguez wrote:
El 27/03/12 20:24, Carlos E. R. escribió:
Oh, how very nice of you, disregarding he fate of your users.
I am not disregarding it, such programs need to use /var/tmp
Ok, so you go out and reprogram all the Linux list of programs
out there. When they fail, you go and mend them. All of them.
That's unreasonable, we can only fix programs included in the
So any program outside the openSUSE distribution which puts huge
files in /tmp become unusable, and most users of those programs are
then forced to use another Linux distro.
Well, Fedora will do a similar switch, so in the future (no idea
when, though), programs will be fixed to use /var/tmp when they rely
on persistent / huge storage for their own data.
/var/tmp is persistent over reboot which is a different use case. Users
or programs writing to /tmp are doing this for a good reason until you
proof for any particular case that they are doing wrong.
And as I wrote in my initial mail, this behavior can be disabled.
Why can't it be enabled keeping the current behaviour per default?
Because I wanted feedback, based on facts (and not just reaction to
changes, like some people seem to do).
I know of one Finite Element code base that uses $TMPDIR to write large temporary files. These files my exceed 10GB. Thus mounting /tmp as tmpfs and having $TMPDIR point to /tmp is not a good solution for this use case. Other solutions in this area of HPC probably behave in a similar fashion.
Sysadmins for systems that are setup to run this code would have to do extra work compared to today's install/setup.
Basically a +1 to the use case Richard described with gcc.
Robert Schweikert MAY THE SOURCE BE WITH YOU
SUSE-IBM Software Integration Center LINUX
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-factory+owner@xxxxxxxxxxxx
|< Previous||Next >|