New subject: [opensuse] back to the 'fix this eternally broken temp file cleanup service' debate

21 Feb 2015

      On 19/02/15 16:56, Joe Zappa wrote:
...
Peter wrote:
...
Bonjour.
This is now driving me mad. Just over a year ago (I had to go hunt
down the thread, here:
http://lists.opensuse.org/opensuse/2014-01/msg00988.html) the issue
was once again raised of why temp files were not being cleaned at boot
(on openSUSE 13.1) if one tried to set the system to do so.
It was established that the cron job configurable from YaST's
sysconfig editor was no longer functional since supposedly being
replaced by the all-round saviour and
tuck-your-sheets-in-would-you-like-a-cup-of-hot-cocoa-with-that
princess that is systemd. Except that the replacement doesn't work. At
least not on any of my 13.1 installations, whereupon both /tmp and
/var/tmp become laden with relics that outright refuse to ever part my
system, gradually filling my root partition until there is no more
room for maneouvre. Currently my /tmp is sitting at 5GB. Looking at
files in there, many are up to a year old. It seems to just accumulate
stuff like an eccentric lonely old man with an attic. This was a fresh
13.1 installation made about a year ago. The root partition (ext4) is
17GB, about half of which was filled after installation. Now there's
little left.
It was also established that SuSE likes to do its SuSEy thing and go
its own way, against systemd defaults, in preserving temp files across
reboots, since some SuSErs want their systems configured that way and
consider /tmp to be a persistent directory.
I've just given up
Now, when I reboot my machines, I log into root and run a shellscript
that I call "start"
which I wrote to do any and all initializations which I USED to put in
in /etc/init.d/local.initializations and then link to from rc{2,3,5}.d
directories
as S99local.initalizations.
But since systemd completely and utterly fucking ignores /etc/init.d/*,
that's out the window.
So is /tmp filling interminably for all users of 13.1 who haven't 
otherwise fiddled with something to prevent this, or who don't have /tmp 
stored in RAM? I don't understand if this is a universal issue/bug or 
it's only affecting certain users, such as those not using btrfs for 
example. Google searches aren't throwing up much in the way of openSUSE, 
only similar issues affecting various other distros.

I don't know what more I can do to empty my /tmp and /var/tmp aside from 
simply rm -rf /tmp. I'm reluctant to do that as a last resort because I 
had problems long ago on this same system after emptying temp, although 
admittedly I stupidly did that whilst running as user with x.

Doing some more plugging I found that

systemctl -l status systemd-tmpfiles-clean.service

was throwing up a failed message concerning gvfs. Thinking this might be 
preventing the service from running, I found a thread on the Arch bug 
tracker (https://bugs.archlinux.org/task/32715) which suggests a 
workaround for this being to create a file, /etc/tmpfiles.d/gvfs.conf 
containing, essentially:

x /run/user/*

to stop systemd going near /run/user at all. Well that changed nothing 
on my system. I've tried manually running

systemd-tmpfiles --clean --remove

but again, though it doesn't return an error, nothing is cleaned up or 
removed. I also notice when running

systemctl -l status systemd-tmpfiles-clean.service

the lines:

    Loaded: loaded 
(/usr/lib/systemd/system/systemd-tmpfiles-clean.service; static)
    Active: inactive (dead)

It seems to always be inactive. Meanwhile, running

systemctl -l status systemd-tmpfiles-setup.service

I get this:

systemd-tmpfiles-setup.service - Recreate Volatile Files and Directories
    Loaded: loaded 
(/usr/lib/systemd/system/systemd-tmpfiles-setup.service; static)
    Active: active (exited) since Sat 2015-02-21 20:17:27 CET; 2min 4s ago
      Docs: man:tmpfiles.d(5)
            man:systemd-tmpfiles(8)
   Process: 356 ExecStart=/usr/bin/systemd-tmpfiles --create --remove 
--exclude-prefix=/dev (code=exited, status=0/SUCCESS)
  Main PID: 356 (code=exited, status=0/SUCCESS)

And I've no idea how to go about setting /tmp to store files for 30 days 
and /var/tmp for 90 like in the good old days, because there's clearly 
not much point even tinkering with that idea until I can get the service 
to run at all. The documentation (man page) for systemd-tmpfiles is 
awful and tells me nothing useful.

I still have 2.5GB to fill on my root partition. I'll keep waiting. 
Before long I'll have to do something.

Peter
-- 
To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org
To contact the owner, e-mail: opensuse+owner@opensuse.org

Re: [opensuse] back to the 'fix this eternally broken temp file cleanup service' debate

Dylan

John Andersen

John Andersen

John Andersen

John Andersen

John M Andersen

John Andersen

John Andersen

John Andersen

John Andersen

tags

participants (14)