https://bugzilla.novell.com/show_bug.cgi?id=721682 https://bugzilla.novell.com/show_bug.cgi?id=721682#c Andreas Jaeger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |nrickert@ameritech.net AssignedTo|bnc-team-screening@forge.pr |ro@suse.com |ovo.novell.com | -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=721682 https://bugzilla.novell.com/show_bug.cgi?id=721682#c3 --- Comment #3 from Neil Rickert 2011-11-18 23:14:04 UTC --- I'm not sure if that NEEDINFO was intended for me. I'm not sure what was being asked by "did you notice root have a special setup" - I initially took that to be a rhetorical question. I see the same problem is several installs, both LVM and plain partitioning. I assume that it is related to "systemd". Presumably, the old scripts that previously interpreted CLEAR_TMP_DIRS_AT_BOOTUP are no longer being run. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=721682 https://bugzilla.novell.com/show_bug.cgi?id=721682#c5 Michael Hofmann changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |michael.hofmann@inode.at --- Comment #5 from Michael Hofmann 2011-11-19 14:12:26 UTC --- I also experience the same problem. System is OpenSUSE 12.1 stable x86_64. Both files from root as well as from normal users are still there after reboot. Some relevant lines from /etc/sysconfig/cron: MAX_DAYS_IN_TMP="0" TMP_DIRS_TO_CLEAR="" OWNER_TO_KEEP_IN_TMP="root" CLEAR_TMP_DIRS_AT_BOOTUP="yes" -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=721682 https://bugzilla.novell.com/show_bug.cgi?id=721682#c7 --- Comment #7 from Michael Hofmann 2011-11-19 15:47:09 UTC --- For the record, booting with SysVinit yields the expected result (/tmp gets cleaned). Accordingly, this is definitely a systemd issue. The init script responsible for the cleanup process is /etc/init.d/boot.cleanup. With systemd, this should apparently be handled by /bin/systemd-tmpfiles. (In reply to comment #6)

Either CLEAR_TMP_DIRS_AT_BOOTUP should work, or the documentation should change to stop mentioning this option. I prefer the first of those choices.

QFT. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=721682 https://bugzilla.novell.com/show_bug.cgi?id=721682#c9 --- Comment #9 from Michael Hofmann 2011-11-21 19:19:00 UTC --- Another workaround is to manually edit /usr/lib/tmpfiles.d/tmp.conf I changed the following line d /tmp 1777 root root 10d => to => D /tmp 1777 root root 1s and now /tmp gets cleaned when booting with systemd. This way however, OWNER_TO_KEEP_IN_TMP is ignored and all files, disregarding their owner, get deleted. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=721682 https://bugzilla.novell.com/show_bug.cgi?id=721682#c11 mike willis changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mike.willis@warwick.ac.uk --- Comment #11 from mike willis 2011-11-27 14:14:42 UTC --- I've added these two lines: cd /etc/init.d/ /boot.cleanup start to /etc/init.d/boot.local and that causes /tmp to be cleared at boot as desired (dependent upon that being set in /etc/sysconfig/cron of course). Just calling /etc/init.d/boot.cleaup results in a message "redirecting to systemctl" and /tmp not being cleared. Setting the working directory to /etc/init.d then calling boot.cleanup with relative path apparently bypasses whatever it is that causes the "redirecting to systemctl" message. I agree with this from comment 6: "Either CLEAR_TMP_DIRS_AT_BOOTUP should work, or the documentation should change to stop mentioning this option. I prefer the first of those choices." I would add that if CLEAR_TMP_DIRS_AT_BOOTUP and similar are removed, equivalent functionality must be provided. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=721682 https://bugzilla.novell.com/show_bug.cgi?id=721682#c13 Tim Edwards changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |iceman@fastmail.com.au --- Comment #13 from Tim Edwards 2011-11-28 13:48:59 UTC --- ""Either CLEAR_TMP_DIRS_AT_BOOTUP should work, or the documentation should change to stop mentioning this option. I prefer the first of those choices." I would add that if CLEAR_TMP_DIRS_AT_BOOTUP and similar are removed, equivalent functionality must be provided." +1 to both these comments. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=721682 https://bugzilla.novell.com/show_bug.cgi?id=721682#c15 --- Comment #15 from Neil Rickert 2011-11-29 20:34:19 UTC --- It's not clear how "/bin/systemd-tmpfiles" would work here. It seems to be for the ongoing clean of temp files, rather than a special case cleanup at boot. My current workaround is to mount "/tmp" with tmpfs. I use this line in "/etc/fstab": none /tmp tmpfs defaults 0 0 Sun solaris has been doing something similar for years, so that might be a good way of eliminating the problem. Here's a tentative proposal: 1: Change the documentation for CLEAR_TMP_DIRS_AT_BOOTUP to indicate that it only applies when booting with sysvinit, and not with systemd. And indicate that its use is deprecated. 2: Add support to Yast for setting up the mounting of “/tmp” from swap. There should be a Yast option with this on the size limit (if desired). Yast would only have to make the changes to “/etc/fstab” and advise the user that they will take effect on reboot. 3: Once this is in Yast, consider adding it as an option in the installer. I posted in more detail at http://nwrickert2.wordpress.com/2011/11/29/cleaning-tmp/ and I would welcome relevant comments there. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=721682 https://bugzilla.novell.com/show_bug.cgi?id=721682#c17 Volker Kuhlmann changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium CC| |volker3204@paradise.net.nz Platform|i686 |All Version|Beta 1 |Final --- Comment #17 from Volker Kuhlmann 2012-02-06 17:25:42 NZDT --- .. and doesn't work properly. You *must* start quota support before you do rm -rf /tmp/* because you really don't want to run quotacheck for every boot. There are two parts to the tmp dir cleaning: one is ocntinually removing files older than X each day, which is done by cron, and the other part is cleaning out directories completely because when booting it's the only time to be able to do it. This is another case where systemd is just a big waste of time. Things just stop working, and since it was reported for beta and is still not working in final it looks like it's a dropped feature. :-(( My vote is definitely on fixing this, rather than on changing the documentation to reflect functionality being lost to another "improvement". -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=721682 https://bugzilla.novell.com/show_bug.cgi?id=721682#c19 Christian Boltz changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |helmut.walle@gmail.com --- Comment #19 from Christian Boltz 2012-05-19 20:42:39 CEST --- *** Bug 762002 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=762002 -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=721682 https://bugzilla.novell.com/show_bug.cgi?id=721682#c20 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |werner@suse.com InfoProvider| |nrickert@ameritech.net --- Comment #20 from Dr. Werner Fink 2013-12-04 20:21:56 UTC --- Is this issue still valid on openSUSE 13.1? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=721682 https://bugzilla.novell.com/show_bug.cgi?id=721682#c22 --- Comment #22 from Benjamin Poirier 2013-12-21 22:49:33 UTC --- (In reply to comment #20)

Is this issue still valid on openSUSE 13.1?

I can confirm that the problem is still present. Moreover, for interested users, here is a way to get the desired behavior via systemd. Create /etc/tmpfiles.d/tmp.conf to override /usr/lib/tmpfiles.d/tmp.conf and edit it according to tmpfiles.d(5). Here is my /etc/tmpfiles.d/tmp.conf, it clears /tmp during boot: # This file is part of systemd. # # systemd is free software; you can redistribute it and/or modify it # under the terms of the GNU Lesser General Public License as published by # the Free Software Foundation; either version 2.1 of the License, or # (at your option) any later version. # See tmpfiles.d(5) for details # Clear tmp directories separately, to make them easier to override D /tmp 1777 root root - d /var/tmp 1777 root root - -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=721682 https://bugzilla.novell.com/show_bug.cgi?id=721682#c Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |vdziewiecki@suse.com |ovo.novell.com | -- 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.

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.

https://bugzilla.novell.com/show_bug.cgi?id=721682 https://bugzilla.novell.com/show_bug.cgi?id=721682#c Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |vdziewiecki@suse.com |ovo.novell.com | -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=721682 https://bugzilla.novell.com/show_bug.cgi?id=721682#c30 Wojtek Dziewięcki changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|vdziewiecki@suse.com |systemd-maintainers@suse.de --- Comment #30 from Wojtek Dziewięcki 2014-05-12 10:11:57 UTC --- I will reassign it to systemd team. If you need me to do something in cron, tell me. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=721682 https://bugzilla.novell.com/show_bug.cgi?id=721682#c32 --- Comment #32 from Volker Kuhlmann 2014-05-12 22:59:28 NZST --- The real problem is that systemd's capabilities with tmpfiles.d do not match the original functionality, and unless I am totally wrong, can not solve the problem. There are at least 2 problems: 1) I am not convinced systemd runs the clearing of tmpdirs at the correct time in the boot sequence. It's too late, potentially wiping important things from daemons starting up etc. 2) Changing systemd targets may leave you suddenly with an empty /tmp. It doesn't seem to want to understand the definition of "at *boot* only, thanks". -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=721682 https://bugzilla.novell.com/show_bug.cgi?id=721682#c35 --- Comment #35 from Bernhard Wiedemann 2014-09-11 12:00:20 CEST --- This is an autogenerated message for OBS integration: This bug (721682) was mentioned in https://build.opensuse.org/request/show/248456 Factory / aaa_base -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=721682 --- Comment #45 from Swamp Workflow Management --- openSUSE-RU-2014:1262-1: An update that has 5 recommended fixes can now be installed. Category: recommended (moderate) Bug References: 721682,860083,861124,880103,882918 CVE References: Sources used: openSUSE 13.1 (src): aaa_base-13.1-16.46.1 -- You are receiving this mail because: You are on the CC list for the bug.