* David C. Rankin <drankinatty@suddenlinkmail.com> [02-23-15 10:49]: [...]
So my only guess is that these are the pieces of the puzzle that are supposed to insure tmpfiles are cleaned. Checking the journal will tell you if they are running. If the only entry in the journal is the gvfs failure without the Starting/Started Cleanup of Temporary Directories..., then figuring out why they are not running will likely solve the issue.
I checked my server which ran out of tmp space recently and see that indeed the cleanup service was started "twice" each day (appears, didn't check that closely except around the failure period). But left over text files from mutt were not cleared/cleaned nor the systemd-private* directories which may have presented an ?? inode problem. Since specifying the time period, the text files *are* clearned but the directories are not. I do not know and cannot find a specified time period for the "persistant/protected" directories.
I don't recall doing anything strange/special on install regarding tmpfiles, although I do go though each config setting and I DO set a traditional 'root' account and password. I've always been leery about not using a traditional root account just for the reason that some hooked process that relies on being run by root -- won't -- in the absence of a traditional root account. I doubt it is related.
I do the same.
Regardless, here is one data-point among others where the cleaning of tmpfiles seems to be working as it should. From the original post, it appears Peter has all parts of the cleanup configuration discussed above. The only additional checks I see are to check the journal and find out just what is being run (and when) and go from there. Further, there should be a way to manually kick-off the cleaning of tmpfiles. I would figure that out and attempt to force a cleaning and check the results/errors there. That will provide a further bit of info.
I also check the journal on a desktop but haven't observed enough time since specifying the time period to make a judgement past the systemd-private* directories remaining. I do see periods of 3-8 days where no cleanup was initiated and single rather than double entries in the journal (one second apart). But subject system is < 2 months old.
Good luck. (SysVinit was so much cleaner...)
In some ways, but I like *much* about systemd. SysVinit was like a manila folder crammed full of random papers and systemd more like an ordered digest. Problem is learning the particular paths vs the remaining rote. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org