On Wed, 04.03.15 16:27, Michael Biebl (mbi...@gmail.com) wrote: > 2015-03-04 15:41 GMT+01:00 Lennart Poettering <lenn...@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 is pulled in implicitly. In many cases dependencies are automatically generated by systemd. For example: you have a mount unit for /tmp/foo and one for /tmp. The former is enabled, the latter is not. Simply because tmp-foo.mount is below tmp.mount this will pull in the latter too and you ened up with both enabled. Similar automatic deps are generated in a variety of cases, for example if you have an AF_UNIX socket, or a pipe socket listening inside of /tmp, you pull in tmp.mount via it. Also, anything that has PrivateTmp= set will pull in tmp.mount, since it implicitly refers to /tmp and /var/tmp. And so on, and so on. Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
