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

Didier Roche didrocks at ubuntu.com
Wed Mar 4 23:36:46 PST 2015

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.


More information about the systemd-devel mailing list