touch-packages team mailing list archive

[Martin Pitt <martin.pitt@xxxxxxxxxx>]

I just have three systemd-private* dirs in /var/tmp/, which is very far
from "enormous". Three because three .service files declare a PrivateTmp
(colord, rtkit-daemon, timesyncd). But they should be cleaned up on shut
down, so supposedly that doesn't happen for you. Would you mind enabling
persistant journal (see /usr/share/doc/systemd/README.Debian),
rebooting, and attaching the journal from the previous boot with

  sudo journalctl -b -1 > /tmp/journal.txt

?

** Changed in: systemd (Ubuntu)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1479732

Title:
  systemd causes mess in /var/tmp

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  There's enormous amount of directories like systemd-private-
  fdd28b0bfe4c47808e41dbb7a0300bdc-colord.service-vrglD7 in /var/tmp

  It's clear why they are necessary but it's still looks irritating and
  is magnified (compared to /tmp for example) by the fact that /var/tmp
  is not cleaned up (and of course it shouldn't be) on every reboot.

  The solution is trivial and already employed by lots of services for
  /tmp - just prepend . to the folder name so it's hidden from user's
  file manager.

  Would be excellent if ubuntu could apply this to systemd as well: the
  lesser is chance for user confusion (those directories are
  unaccessible to the user anyway so there's little sense in showing
  them) - the better.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1479732/+subscriptions