On 18/02/2020 21.28, Dave Howorth wrote:
On Tue, 18 Feb 2020 19:29:05 +0100 "Carlos E. R." <> wrote:
On 18/02/2020 18.11, Dave Howorth wrote:
On Tue, 18 Feb 2020 12:37:37 +0100 "Carlos E. R." <> wrote:
On 18/02/2020 12.26, Dave Howorth wrote:
On Tue, 18 Feb 2020 12:08:59 +0100 Peter Suetterlin <> wrote:
Ianseeks wrote:
> I've got a pretty much stock set up and my tmp directory was > full of months old stuff and the same went for the journals so > it doesn't seem set up for automatic housekeeping out of the > box.
I think tmp is indeed not cleaned (on purpose, IIRC).
https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch03s18.html
"Although data stored in /tmp may be deleted in a site-specific manner, **it is recommended that files and directories located in /tmp be deleted whenever the system is booted.**"
My /tmp gets very large as well particularly with stuff from firefox so I don't think openSUSE clears it at boot properly.
Intentionally so, I understand. The old setting, pre-systemd, was to delete aged files (I think there was a configuration setting to do at boot). After systemd, it is broken, because the recommended systemd thing is to have /tmp on ram, and we don't by default (intentionally, we users demanded this).
I don't understand what systemd has to do with it. FHS says:
Forget what the FHS says. This was redesigned with the advent of systemd, and that is a fact.
Reference?
My memory. Seek this list archive. :-D My memory is not as good as it was, but I do remember that we discussed this for weeks. Notice that I'm not referring (exclusively) to systemd devs. I'm referring mostly to the consequences of systemd advent, how openSUSE responded and how it applied things, how the community reacted, what was finally done. See the highlighted line below as proof:
When I look in /usr/lib/tmpfiles.d/tmp.conf I see:
# Clear tmp directories separately, to make them easier to override # SUSE policy: we don't clean those directories <================ q /tmp 1777 root root - q /var/tmp 1777 root root -
So I think the blame is quite clearly laid at SUSE's door. Can anybody tell me where this policy of SUSE's that contradicts FHS is (a) defined and (b) explained? Also how do I set the system to clear /tmp on reboot?
We insisted on this behaviour was wanted on the mail lists, the SuSE way.
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?
Many reasons I don't remember :-) For example, downloads happening there. Scripts that save files there. Not saying good or bad, they just do.
A URL to the appropriate mail thread archive would likely help me understand.
I would have a tremendous job seeking the archive for some hundreds of posts. Yet, some: Date: Mar 2012 13:53:20 +0200 Cc: opensuse-factory@opensuse.org Subject: Re: [opensuse-factory] to tmp-on-tmpfs or not tmp-on-tmpfs There was a blog: http://jaegerandi.blogspot.de/2012/03/tmp-as-tmpfs-for-opensuse.html Now it asks for password.
Oh and note that the note in the file says 'SUSE' not 'openSUSE', which makes me even more curious.
Well, both did the same thing, which I like. :-D -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.1 (Legolas))