В Sun, 5 May 2013 15:39:59 +0200 Marcus Meissner <meissner@suse.de> пишет:
On Sun, May 05, 2013 at 09:28:41AM -0400, Anton Aylward wrote:
Carlos E. R. said the following on 05/05/2013 09:03 AM:
Take a look at /etc/cron.daily/suse.de-clean-tmp and at /etc/sysconfig/cron
That is deprecated and does not work. It doesn't, because those files are owned by root. And it doesn't because if systemd is running the cron job does not work. See release notes:
My Bad. Thank you for the correction. I looked on my 12.2 system rather than 12.3. I see that /etc/cron.daily/suse.de-clean-tmp isn't there on my 12.3 system.
Sadly /etc/sysconfig/cron is. Hmm, that was a clean install on the 12.3 machine I'm looking at so I can't blame it on being a residue of an update.
That still doesn't answer why they got created and left behind in the first place. You point out that programs _should_ clean up after themselves, but I've never relied on that. "Evidence".
I suspect this is the "PrivateTmp=true" feature of systemd, where systemservices get their own /tmp to avoid generic tmp race attacks.
So basically a security feature.
No idea about how the clean up works there, if it does not, report a bug I would say :/
Unfortunately in version we have these directories were created far too late to remove them in place (they were created in child right before exec so there was no code to remove them) and removing them during periodic cleanup is probably wrong as well (they may belong to long running service processes). In current upstream they are created differently and cleaned up when service stops. There is still corner case when system crashes and leaves those directories behind. So I think we still need to at least clean them up on reboot. bor@opensuse:~> cat /etc/tmpfiles.d/remove-systemd-private.conf R /tmp/systemd-private-* R /var/tmp/systemd-private-* -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org