https://bugzilla.novell.com/show_bug.cgi?id=721682
https://bugzilla.novell.com/show_bug.cgi?id=721682#c27
--- Comment #27 from Volker Kuhlmann 2014-01-24 11:40:40 NZDT ---
This bug is about clearing temp dirs at bootup not having been functional on
any oS version with systemd. It doesn't have much to do with cron, and a
solution can probably only be achieved with systemd.
Werner might have missed the nature of this bug report when talking about tmp
file handling by cron (periodic cleaning). That's only part of the tmp file
handling. The OTHER part is cleaning the whole lot of tmp rubbish AT BOOT,
which has never involved cron and was always done by the init system.
I use a slightly more elaborate /etc/tmpfiles.d/tmp-local.conf
D /tmp 1777 root root 7d
d /var/tmp 1777 root root 60d
r /var/tmp/rpm-tmp.??????
r /var/tmp/TmpDir.??????
r /var/tmp/zypp.??????
# Exclude namespace mountpoints created with PrivateTmp=yes
X /tmp/systemd-private-*
X /var/tmp/systemd-private-*
It deals with both periodic cleaning and cleaning at boot.
Unfortunately it is not an equivalent to the old semantics. I am never quite
sure where exactly in the boot process the rm -rf /tmp/* happens; with init.d
this happened safely before any runlevels were entered. With systemd it happens
as part of entering its "runlevels", which may or may not cause timing issues.
It's also dangerous in other cases: When changing runlevels with systemd one
suddenly has a very empty /tmp, which was definitely neither wanted nor
desired! If I want to be silly and clear /tmp at runtime I can always use rm
-rf, which is effectively what systemd is doing with the above confirguration.
IMNSHO systemd should never have been unleashed on unsuspecting Linux systems
until reaching some level of maturity (and a fraction of its complexity).
Werner re comment#20: This issue remains valid on all suse versions until
systemd is kicked into shape.- the configs suggested above are still
unsatisfactory.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.