В Mon, 23 Feb 2015 12:27:16 -0500 Patrick Shanahan <paka@opensuse.org> пишет:
* Andrei Borzenkov <arvidjaar@gmail.com> [02-23-15 12:23]:
В Mon, 23 Feb 2015 12:18:18 -0500 Patrick Shanahan <paka@opensuse.org> пишет:
* Andrei Borzenkov <arvidjaar@gmail.com> [02-23-15 12:06]:
В Mon, 23 Feb 2015 11:22:20 -0500 Patrick Shanahan <paka@opensuse.org> пишет:
The files below /usr/lib/tmpfiles.d/ indicate a 30d default for the most part, but do not show what I was looking for, time for removing stale systemd-private* directories
I think it was discussed on this list already. It is not safe to delete them because it is not known whether they belong to a running service. Current upstream version now removes these directories when service stops (change is rather intrusive to integrate in version used by 13.2). This leaves us with directories left as result of system crash which can be (unless already done) removed on startup.
I believe among packages in default installation there are probably couple of those using systemd-private-* directories and I'm not sure whether they are even enabled by default. So unless you permanently restart them it hardly can be considered an issue. On startup I delete them with
bor@opensuse:~> cat /etc/tmpfiles.d/remove-systemd-private.conf R /tmp/systemd-private-* R /var/tmp/systemd-private-* bor@opensuse:~>
Tks, I will institute that on my desk/laptops but what do you do on a server?
I'm not sure I understand the question.
I make every effort to not "reboot" servers.
How often services that are using private tmp directories are restarted on your servers? If this happens so often as to become a problem, you can install systemd from factory. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org