Re: [opensuse] Re: systemd: are there exceptions for cleaning up tmpfiles.d stuff?

Am Dienstag, 11. Februar 2014, 14:18:22 schrieb Joachim Schrod:

On 02/11/14 03:22, Andrey Borzenkov wrote:

...

В Tue, 11 Feb 2014 01:51:11 +0100

Joachim Schrod пишет:

...

Hi,

My /usr/lib/tmpfiles.d/tmp.conf has the line

d /tmp 1777 root root 10d

That's not default in openSUSE. Did you change it manually? It will be lost on update.

No, I didn't change it. [...]

Then you are not using 13.1. :)

puma:/usr/lib/tmpfiles.d # ll -t /tmp | tail -2 -rw-rw-r-- 1 schrod npc 9402 Feb 4 22:48 dc.diff drwx------ 2 root root 4096 Jan 29 00:50 ssh-ak8TJJmMZc puma:/usr/lib/tmpfiles.d # ll -a /tmp/ssh-ak8TJJmMZc total 16 drwx------ 2 root root 4096 Jan 29 00:50 . drwxrwxrwt 43 root root 12288 Feb 11 14:07 .. srwxr-xr-x 1 root root 0 Jan 29 00:50 agent.2528 puma:/usr/lib/tmpfiles.d # uptime 14:08pm up 6 days 14:38, 4 users, load average: 0.40, 0.30, 0.21

That dir should have been deleted in the mean time, shouldn't it?

Well, I think so. Does a manual "systemd-tmpfiles --clean" delete it?

As I wrote above, I want to learn how that works.

Effectively, the old-age clean task is done by "systemd-tmpfiles --clean", if I interpret the man pages correctly. -- Who calls that command? systemd? -- In what frequency? -- Is that call/frequency configured somewhere? [...]

man systemd.timer There is a systemd-tmpfiles-clean.service that is controlled by systemd- tmpfiles-clean.timer. By default, the former is started 15 minutes after a boot and after 1 day it was last activated. So, you can use "systemctl status systemd-tmpfiles-clean.timer" to see when the timer has triggered and "systemctl status systemd-tmpfiles- clean.service" when the cleanup actually started. Gruß Jan -- There is no such thing as a "free lunch". (only a choice of restaurants) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org