Where is Slackware's "per user tmp that should survive reboots"?

Hello, everyone.

I need advice on where to put a file that records when I last made a backup.

Now I put it into /run/user/$uid , which is not too bad, but does not survive reboots.

Potential directories include "/var/tmp/user/$pid", "~/.local/var/tmp", ~/.local/tmp", or whatever I haven't thought about.

What is the Slackware way of keeping these files?

Hi,

Your /home directory seems to be appropriate

For per user I'd consider ~/.local/share/

For system wide I'd consider /var/lib/ or /var/log/

Traditional Linux systems have user writable /tmp, Slackware does not? Or it is in tmpfs and won't survive reboot?

You can try logger(1) from a script or syslog(3) if from a program. Then you can leverage the existing logrotate(8) setup in Slackware.

Originally Posted by Emerson Traditional Linux systems have user writable /tmp, Slackware does not? Or it is in tmpfs and won't survive reboot?

Slackware does have /tmp ! It is not by default in tmpfs or volatil fs. It has no rule to delete after some time as in Centos.

But some folks like me put their /tmp in tmpfs.

For savings, I will store adm datas in the home of the user which does the task in a directory dedicated to that task.

I don't think there's a Slackware way for this a Slackware don't fiddle with $HOME. To illustrate this, in Slackware-current:

didier[/slackware]$ find etc/skel/ 
etc/skel/
etc/skel/.screenrc
didier[/slackware]$

You could just put the file in some folder in ~/.local that you deem appropriate. You just need to remember where you put it.

What Slackware 'man hier' tells about it?

I agree with Didier Spaier. However, I see per-user directories for kdecache in /var/tmp with content that certainly survived many reboots. Maybe you could do it in a similar way. The other option coming to my mind would be to use syslog and exclude the file from log rotation. Check /etc/logrotate.d for examples.