Mailinglist Archive: opensuse-factory (435 mails)

< Previous Next >
Re: [opensuse-factory] Proposal: /tmp as tmpfs
On 2020-07-11 17:05, Richard Brown wrote:
On Sat, 2020-07-11 at 16:55 +0200, Bernhard Voelker wrote:
On 2020-07-10 22:25, Cristian Rodríguez wrote:
you unfortunately cannot trust software to clean after themselves..
this is the sad state of things and one of the main reasons this
to be done, as long as something uses the mk*stmp* tmpn* interfaces
will continue happen. (tmpfile() now uses O_TMPFILE so it is
from nasties list)

A problem is when a program which creates temporary files can't know
they have to be deleted later, e.g. a mail program saving an
and then starting an application to display it.

The FHS and POSIX standards are very clear on this.

The standard might be clear, but that still does not clarify which program
is responsible for deletion. As a concrete example: Thunderbird saves a
PDF file and starts Evince to open it.

No application should expect a file in /tmp to be there after the
current execution of the application.

There's no golden rule when would be the best time to delete the
but IMO a time-based rule (e.g. a week) is better than a reboot-based
cleanup ... especially on Tumbleweed where we boot quite often due to

Given the recommendations of the FHS and the hard requirement of the
POSIX standard, then any reboot is _the_ perfect time to clean up /tmp,
because it's the one time we can be sure there is nothing currently
executing, therefore nothign can be using /tmp at that time.

Just for the record: I'm not really pro or contra the change to /tmp as
/tmpfs. It's just that in my opinion, none of the given reasons are really
forcing us to do the change. We _can_ do it, and maybe it's the right
time to it now.

Reading all the posts so far, I'd say nobody is against the change
... as long as a user can choose something different for his/her

Have a nice day,
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-factory+owner@xxxxxxxxxxxx

< Previous Next >
This Thread
Follow Ups