I was watching a blueray movie that came from a compressed archive, so when I run it directly from ark it gets placed in /tmp
.
I got an idea about a thing and to find out if it worked I had to logout/in again so I closed the movie and did just that.
When coming back I thought to myself, “oh ■■■■” I now have to unpack this HUGE file again, but mark my surprise when the file was still there after my logout/in.
So I did a test to confirm it was not just a fluke.
dd bs=1024 count=1048576 if=/dev/urandom of=/tmp/file.tmp status=progress
Logged out, switched tty, logged in and:
$ ls -l /tmp
-rw-r--r-- 1 bedna bedna 1073741824 Dec 29 15:10 file.tmp
drwx------ 2 bedna bedna 40 Dec 29 12:40 plasma-csd-generator.FJWDtd
drwx------ 2 bedna bedna 40 Dec 29 15:00 plasma-csd-generator.lTnzxB
srwx------ 1 sddm sddm 0 Dec 29 15:11 sddm-:0-KLLyMQ
srwxr-xr-x 1 root root 0 Dec 29 12:40 sddm-auth-c1e8cca7-33df-4bf9-a5aa-66dd511fb9a7
drwx------ 2 root root 40 Dec 29 12:40 snap-private-tmp
drwx------ 3 root root 60 Dec 29 12:40 systemd-private-75ee6b86d5a942d8b4fe56031eb846db-bluetooth.service-938igF
drwx------ 3 root root 60 Dec 29 12:40 systemd-private-75ee6b86d5a942d8b4fe56031eb846db-ModemManager.service-XYGc29
drwx------ 3 root root 60 Dec 29 12:40 systemd-private-75ee6b86d5a942d8b4fe56031eb846db-polkit.service-02teRc
drwx------ 3 root root 60 Dec 29 12:40 systemd-private-75ee6b86d5a942d8b4fe56031eb846db-portmaster.service-s7x51r
drwx------ 3 root root 60 Dec 29 12:40 systemd-private-75ee6b86d5a942d8b4fe56031eb846db-systemd-logind.service-R2t1ml
drwx------ 3 root root 60 Dec 29 12:40 systemd-private-75ee6b86d5a942d8b4fe56031eb846db-systemd-timesyncd.service-Y6mOvJ
drwx------ 3 root root 60 Dec 29 12:40 systemd-private-75ee6b86d5a942d8b4fe56031eb846db-upower.service-BeRKhd
-rw------- 1 sddm sddm 102 Dec 29 15:11 xauth_irfxav
So should not /tmp
get emptied on logout?
$ ls -l -d /tmp
drwxrwxrwt 18 root root 660 Dec 29 15:13 /tmp
EVERYTONE has access to it. (although the files not made by me is (except sddm-auth-c1e8cca7-33df-4bf9-a5aa-66dd511fb9a7
that is a symlink), but still?)