On 19/02/2020 12.45, Dave Howorth wrote:
On Wed, 19 Feb 2020 11:20:18 +0100 "Carlos E.R." <robin.listas@gmx.es> wrote:
On 19/02/2020 05.54, Anton Aylward wrote:
On 18/02/2020 15:28, Dave Howorth wrote:
For Dog's sake, WHY? Why would anybody want to keep a temporary file from before the system was booted? And if they did, why not put it in /var/tmp like they're supposed to?
Good question.
If we are talking about a personal system, a workstation, not a server, that is, for example, booted each morning and shutdown when you leave for work after reading your mail, then rebooted in the even of a bit of 'perusal', and 'all day' at weekend or holidays .... a "Linux instead of Windows" PC machine ...
Example situation.
You use firefox to view a pdf in a tab. Powerdown for the night, or because maintenance or whatever. Includes a save session. On session restore, the tab has lost the pdf.
Why? Because the pdf was downloaded to /tmp, and it was erased.
Firefox doesn't download to /tmp, it downloads to wherever you tell it to. So choose somewhere else if you want to keep it!
I may have done it ages ago and it reverted on its own another year. I don't mind. /tmp is SSD in my case, /home is not. Notice it is not the "download" file function. It is the view pdf file, and it does not ask.
Or...
run save_y2logs which takes time to run, saves to /tmp. Days later I get some information and want to check file. It is lost.
Again, give save_y2logs a permanent location if that's what you want.
I like it there, temporarily :-) It will be deleted eventually. Just not on boot.
The assumption that /tmp will be deleted on boot does not exist in many cases.
I don't know what that means?
It is rather "it will be deleted eventually".
Well, that the programmers of whatever that used /tmp did not assume that it would be deleted always on the next boot. The FHS may chant mass if they like, but it is not law. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)