Bug 10203 - Systemd leaves empty directories systemd-private-xxxxx in /var/tmp/
Summary: Systemd leaves empty directories systemd-private-xxxxx in /var/tmp/
Status: RESOLVED WONTFIX
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 3
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Colin Guthrie
QA Contact:
URL:
Whiteboard:
Keywords: Triaged
Depends on:
Blocks:
 
Reported: 2013-05-21 22:30 CEST by dave pickles
Modified: 2014-05-12 17:36 CEST (History)
0 users

See Also:
Source RPM: systemd-195-22.mga3
CVE:
Status comment:


Attachments

Description dave pickles 2013-05-21 22:30:52 CEST
Description of problem:
The /var/tmp directory is accumulating empty directories with names 'systemd-private-xxxxx'; there are over 400 at present and growing at about 10 per day.

Version-Release number of selected component (if applicable):
Presumably these files are created by systemd.

How reproducible:
Happens on both machines currently running Mageia 3.

Temporary files created by systemd are supposed to be purged by /usr/lib/tmpfiles.d/tmp.conf, however names matching /var/tmp/systemd-private-* are specifically excluded from deletion.

Fedora bug 884344 seems to match this issue.


Reproducible: 

Steps to Reproduce:
Manuel Hiebel 2013-05-21 22:34:41 CEST

Keywords: (none) => Triaged
Assignee: bugsquad => mageia

Comment 1 David Walser 2013-08-10 20:57:29 CEST
Fixed by Fedora in systemd 201 according to:
https://bugzilla.redhat.com/show_bug.cgi?id=884344
Comment 2 Colin Guthrie 2014-05-12 17:36:40 CEST
So yeah, this is ultimately fixed in newer systemd's so after upgrade to MGA4 they should all be tidied away nicely.

It's likely several patches so I won't go through them all and find the right ones unless someone screams really loudly and threatens to kill some kittens.

Status: NEW => RESOLVED
Resolution: (none) => WONTFIX


Note You need to log in before you can comment on or make changes to this bug.