Bug 957439
| Summary: | systemd private directories are not removed | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | udo <udovdh> |
| Component: | systemd | Assignee: | systemd-maint |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 19 | CC: | johannbg, lnykryn, metherid, mschmidt, msekleta, notting, plautrba, systemd-maint, udovdh, vpavlin, zbyszek |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | systemd-208-6.fc20 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-11-24 23:48:18 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
udo
2013-04-28 07:22:16 UTC
This is fixed in F19. Fixes for this one and a related bug 866693 would be nice to backport to F17, but I haven't had the time for it. It's not a trivial cherry-pick. If someone else is willing to produce an F17 update, feel free. This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. I'll wait for the right time to check the fix... Still happening in Fedora 19. I'd like to modify the template so that the private directories have a meaningful name ("/tmp/systemd.service-name.service.23dfjs943" or something like that). This will help diagnose what/if directories are being left behind, and will of course also be nicer for the administrator.
I'm pretty sure that this is fixed now, I haven't seen those in a while, but I'm leaving this open until we're sure.
(In reply to Zbigniew Jędrzejewski-Szmek from comment #6) > I'd like to modify the template so that the private directories have a > meaningful name ("/tmp/systemd.service-name.service.23dfjs943" Nevermind. I've now pushed a change to do that, but it's not necessary here, I think. It seems that those directories are from mysql and colord. > Still happening in Fedora 19. udo, can you post an updated listing of left-over directories? Is there anything in them? systemd should either remove all directories when units are stopped, or log warnings. Can you check if there are any warnings like "Failed to remove content of temporary directory ..." or "Failed to remove temporary directory ..."? # ls -tl total 120 drwx------ 2 udo udo 4096 Oct 26 15:42 plugtmp-3 drwx------ 2 udo udo 4096 Oct 26 15:08 flashgot.3vpe9gc7.default drwx------ 3 root root 4096 Oct 26 15:05 systemd-private-CbLGqR -rw------- 1 udo udo 23939 Oct 25 16:38 9360s7yP.rpm.part drwx------ 2 udo udo 4096 Oct 23 16:50 plugtmp-1 -rw------- 1 udo udo 48897 Oct 22 18:34 2dqkCOvY.gz.part -rw------- 1 root root 995 Oct 22 15:26 rpm-tmp.TUaXZm drwx------ 2 udo udo 4096 Oct 22 15:04 plugtmp-11 drwx------ 2 udo udo 4096 Oct 21 17:42 plugtmp-2 drwx------ 2 udo udo 4096 Oct 20 12:59 plugtmp drwxr-xr-x 82 abrt abrt 4096 Oct 20 06:20 abrt drwx------ 2 udo udo 4096 Oct 14 17:51 plugtmp-10 drwxr-xr-x. 19 root root 4096 Oct 13 18:40 ccache drwx------ 2 udo udo 4096 Jan 1 1970 orbit-udo # w 16:31:44 up 2 days, 23:33, 5 users, load average: 0.54, 0.70, 0.72 (etc) # ls systemd-private-CbLGqR/ tmp # ls systemd-private-CbLGqR/tmp/ # One systemd-private-* dir is OK. systemd-208-6.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/systemd-208-6.fc20 Package systemd-208-6.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-208-6.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-21935/systemd-208-6.fc20 then log in and leave karma (feedback). systemd-208-6.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report. |