On Fri, 14 Jul 2017 12:28:20 +0200, Michael Biebl wrote: > 2017-07-14 12:24 GMT+02:00 Mantas Mikulėnas <graw...@gmail.com>: >> On Fri, Jul 14, 2017 at 12:13 PM, Richard W.M. Jones >> <rjo...@redhat.com> wrote: >>> >>> >>> https://github.com/systemd/systemd/issues/6334 >>> >>> Since this commit >>> >>> https://github.com/systemd/systemd/ commit/2d058a87ffb2d31a50422a8aebd119bbb4427244 >>> (in v233 and v234), you can no longer create >>> /etc/systemd/system/default.target.wants/ and drop in service files >>> (or symlinks). The directory is skipped. I have reverted the commit >>> on top of systemd from git and that makes defaults.target.wants work >>> again. >>> >>> Is this supposed to work? It worked fine since at least Fedora 18-25, >>> but it is now broken in Fedora 26. >>> >>> If it was never supposed to work, how are you supposed to enable a >>> service for the default target, even allowing for the user to change >>> the default target and still have the service enabled? >> >> >> The current convention is to install all regular services into >> multi-user.target, and I would expect all custom "daily use" targets to >> be superset of multi-user.target as well, like the provided >> graphical.target already is. > > Seems like default.target is used by quite a few services though: > https://codesearch.debian.net/search?q=WantedBy%3Ddefault.target > > If default.target is not supposed to be used, then this should be > mentioned somewhere.
The user manager has a real default.target. Many (most?) of the units listed above are user services. -- Saludos, Felipe Sateler _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
