https://bugzilla.novell.com/show_bug.cgi?id=721682
https://bugzilla.novell.com/show_bug.cgi?id=721682#c6
Neil Rickert changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |NEW
InfoProvider|nrickert@ameritech.net |
--- Comment #6 from Neil Rickert 2011-11-19 14:40:43 UTC ---
There are the cron settings to delete unused files after a while. And yes,
MAX_DAYS_IN_TMP is 0, so that is disabled. But the CLEAR_TMP_DIRS_AT_BOOTUP is
a separate control, and was independing of normal cron operations. That's the
one that is not working.
Presumably, this is due to the switch to "systemd" in place of "init", so that
the old init scripts that interpreted that setting are no longer in use.
If the current plan is to ignore CLEAR_TMP_DIRS_AT_BOOTUP, then you at least
have a documentation bug, since it is described as working. Based on posts in
the forums, I'd say that some users depend on this because they run
applications that fill up "/tmp".
Personally, I find CLEAR_TMP_DIRS_AT_BOOTUP to be useful, even if not essential
to how I do things. Bootup, before anything begins to use "/tmp" is the
natural time to clear stuff out.
Note to Michael Hofmann. Maybe try using F5 on the grub boot screen, and
select to boot with "init". The CLEAR_TMP_DIRS_AT_BOOTUP might work that way.
You could use that as a fallback when clearing out "/tmp" is important.
My current workaround is to mount "/tmp" from tmpfs. That way, it is freshly
created at each boot.
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.
--
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.
