Bug#779169: systemd >=219-1 doesn't clean up /tmp/ on reboot

[Stefan Lippers-Hollmann]

Package: systemd
Version: 219-1
Severity: minor

Hi

Starting with systemd >=219-1 (including 219-3), I notice that /tmp/ 
isn't cleaned up while rebooting anymore (stale directories and files 
remain, at least back to 2016-02-18, when I upgraded from 218-10 
to >= 219-1), which was working as expected up to and including 218-10.

Looking through the debdiff between 218-10 and 219-3, the following 
commit jumps out:

commit 8b9c316708dcc3c92c00b5fcd3dc202cd20fc430
Author: Martin Pitt <martin.pitt at ubuntu.com>
Date:   Tue Feb 17 07:50:22 2015 +0100

    New upstream release 219
[...]
diff --git a/debian/patches/Bring-tmpfiles.d-tmp.conf-in-line-with-Debian-defaul.patch b/debian/p
atches/Bring-tmpfiles.d-tmp.conf-in-line-with-Debian-defaul.patch
index e63a657..a840694 100644
--- a/debian/patches/Bring-tmpfiles.d-tmp.conf-in-line-with-Debian-defaul.patch
+++ b/debian/patches/Bring-tmpfiles.d-tmp.conf-in-line-with-Debian-defaul.patch
[...]
 --- a/tmpfiles.d/tmp.conf
 +++ b/tmpfiles.d/tmp.conf
 @@ -8,8 +8,8 @@
  # See tmpfiles.d(5) for details
  
  # Clear tmp directories separately, to make them easier to override
--d /tmp 1777 root root 10d
--d /var/tmp 1777 root root 30d
-+D /tmp 1777 root root -
-+#d /var/tmp 1777 root root 30d
+-v /tmp 1777 root root 10d
+-v /var/tmp 1777 root root 30d
++v /tmp 1777 root root -
++#v /var/tmp 1777 root root 30d
  
  # Exclude namespace mountpoints created with PrivateTmp=yes
  x /tmp/systemd-private-%b-*
[...]

Overriding tmp.conf back to specify

d /tmp 1777 root root -

does indeed restore the original behaviour of properly cleaning
/tmp/ while booting.

This is occuring on multiple systems for me, most including lvm2
and (all) an ext4 filesystem mounted or bind-mounted at /tmp/, but I 
can easily reduce this to a simple test case using a single ext4 
partition for the whole system in a kvm virtual machine.

$ cat /etc/fstab 
UUID=a6a62fc2-14bc-4927-a2b7-afe5a65b62cc     /                    ext4         defaults,relatime,errors=remount-ro           0    1

As I don't see this mentioned as an intentional change in the (Debian's)
changelog, I assume that this might have been an unintentional 
modification. Feel free to close this bug if it was indeed an intentional
change of behaviour.

Regards
	Stefan Lippers-Hollmann

-- Package-specific info:

-- System Information:
Debian Release: 8.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (200, 'testing'), (101, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.19.0-0.slh.1-aptosid-amd64 (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages systemd depends on:
ii  adduser         3.113+nmu3
ii  initscripts     2.88dsf-58
ii  libacl1         2.2.52-2
ii  libapparmor1    2.9.0-3+exp1
ii  libaudit1       1:2.4-1+b1
ii  libblkid1       2.25.2-5
ii  libc6           2.19-15
ii  libcap2         1:2.24-6
ii  libcap2-bin     1:2.24-6
ii  libcryptsetup4  2:1.6.6-5
ii  libgcrypt20     1.6.2-4+b1
ii  libkmod2        18-3
ii  liblzma5        5.1.1alpha+20120614-2+b3
ii  libmount1       2.25.2-5
ii  libpam0g        1.1.8-3.1
ii  libselinux1     2.3-2
ii  libsystemd0     219-3
ii  mount           2.25.2-5
ii  sysv-rc         2.88dsf-58
ii  udev            219-3
ii  util-linux      2.25.2-5

Versions of packages systemd recommends:
ii  dbus            1.8.16-1
ii  libpam-systemd  219-3

Versions of packages systemd suggests:
pn  systemd-ui  <none>

-- no debconf information
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: Digitale Signatur von OpenPGP
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20150225/a5d99b45/attachment.sig>