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: Ruediger Meier <sweet_f_a@xxxxxx>
- Date: Wed, 28 Mar 2012 11:31:46 +0100
- Message-id: <201203281231.47102.sweet_f_a@gmx.de>
On Wednesday 28 March 2012, Frederic Crozat wrote:
No, data which is not needed after reboot is wrong in /var/tmp. It's the
decision of the data producer where to put it. Keep in mind that anyone
who is writing to /tmp is doing this for a good reason.
What you are trying to "fix" is "don't use /tmp because it's unusable
now".
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-factory+owner@xxxxxxxxxxxx
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.
No, data which is not needed after reboot is wrong in /var/tmp. It's the
decision of the data producer where to put it. Keep in mind that anyone
who is writing to /tmp is doing this for a good reason.
What you are trying to "fix" is "don't use /tmp because it's unusable
now".
--And this is assuming users can override this decision and use a
regular filesystem as /tmp.
As I wrote in my initial email (but few people read it completely
apparently), it is possible..
--
Frederic Crozat <fcrozat@xxxxxxxx>
SUSE
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-factory+owner@xxxxxxxxxxxx
| < Previous | Next > |