[systemd-devel] Possible bug when a dummy service declares After= and/or Conflicts= a .mount unit?

Lennart Poettering lennart at poettering.net
Thu Mar 5 03:26:53 PST 2015

On Thu, 05.03.15 08:36, Didier Roche (didrocks at ubuntu.com) wrote:

> Le 04/03/2015 16:27, Michael Biebl a écrit :
> >2015-03-04 15:41 GMT+01:00 Lennart Poettering <lennart at poettering.net>:
> >>Well, just removing the symlink is kinda pointless. It might still be pulled
> >>in by anything else that implicitly depepends on /tmp.
> >What unit is supposed to pull in tmp.mount explicitly? If a generic
> >unit did that, this sounds like a bug.
> >
> >
> It seems to be systemd-timesyncd.service. I still don't have an answer why
> it's sometimes activated in my kvm env (and rightly, with condition
> virtualized failing) and most of the time none. I'll try to spend some time
> on that before the end of week.

systemd-timesyncd.service has PrivateTmp= set, which will cause it to
be pulled in.


Lennart Poettering, Red Hat

More information about the systemd-devel mailing list